AS44973 RZHAS-AS Rechenzentrum Hassfurt GmbH
🇩🇪Org handle: ORG-sIHG1-RIPE
Rechenzentrum Ha�furt GmbH
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 6/100 · Low riskRPKI ROA coverage
100%
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 44/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 3 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 93.88.224.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 185.130.8.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 2a02:218::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 3 announced prefixes of AS44973 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS44973 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS44973 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/44973Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44973" | jq