AS201697 SEMAPHOR-AS Tobias Fonsmark trading as Semaphor
🇩🇰Org handle: ORG-TFTA5-RIPE
Semaphor ApS
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 35/100 · Medium riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- 100% of announced prefixes (4 of 4) have no valid ROA
Based on 4 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-24 | |
| No ROA | RIPE | 2026-10-24 | |
| No ROA | RIPE | 2026-10-24 | |
| No ROA | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.156.8.0/22 | 🇩🇰 DK | RIPENCC | allocated |
| 195.190.25.0/24 | 🇩🇰 DK | RIPENCC | assigned |
| 2001:678:72c::/48 | 🇩🇰 DK | RIPENCC | assigned |
| 2a10:b1c0::/29 | 🇩🇰 DK | RIPENCC | allocated |
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 AS201697 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/201697Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201697" | jq