AS48447 Sectigo Sectigo Limited
🇬🇧Org handle: ORG-SL842-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,816
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.183.44.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 91.199.212.0/24 | 🇬🇧 GB | RIPENCC | assigned |
| 91.209.196.0/24 | 🇬🇧 GB | RIPENCC | assigned |
| 91.212.12.0/24 | 🇬🇧 GB | RIPENCC | assigned |
| 185.93.12.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 2a0e:ac00::/32 | 🇬🇧 GB | RIPENCC | allocated |
All 5 announced prefixes of AS48447 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS48447 hands its own prefixes to: transit providers, or peers at an exchange.
- AS174Cogent Communications5
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS48447 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/48447Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48447" | jq