Network · data from 2026-11-12
AS48447 Sectigo Sectigo Limited
Registry name: Sectigo Sectigo Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48447, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 5.183.44.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.199.212.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 91.209.196.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 91.212.12.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a0e:ac00::/32 | No ROA | RIR databaseRIPE | 633 100% |
AS-SET
AS48447 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.
- ROA: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.183.44.0/22 | No ROA covers it. Add a ROA for AS48447, maxLength 22. |
| ROA: none | 91.199.212.0/24 | No ROA covers it. Add a ROA for AS48447, maxLength 24. |
| ROA: none | 91.209.196.0/24 | No ROA covers it. Add a ROA for AS48447, maxLength 24. |
| ROA: none | 91.212.12.0/24 | No ROA covers it. Add a ROA for AS48447, maxLength 24. |
| ROA: none | 2a0e:ac00::/32 | No ROA covers it. Add a ROA for AS48447, maxLength 32. |
Route objects not announced
Route objects with origin AS48447 whose prefix no peer sees AS48447 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.23.50.0/23 | ALTDB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.