DF Horus
DF-NAT
Data as of 2026-09-27
BGP inherited
This organisation
| Netblocks | 3 · 1,536 IPv4 addresses |
| Also registered under this name | 4 netblocks across 2 separate records |
| Record ID | 247830163 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.178.214.0/24 | DF-NAT | RIPE | ASSIGNED PA | ● low |
| 178.178.215.0/24 | DF-NAT | RIPE | ASSIGNED PA | ● low |
| 217.198.89.0 – 217.198.92.255 | DF_NAT | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (2)
These blocks are registered to DF Horus but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 178.178.214.0/24 /24 | authorized for AS31133 — PJSC MegaFon |
| 178.178.215.0/24 /24 | authorized for AS31133 — PJSC MegaFon |
NIC Handles
DUMY-RIPE
DUMY-RIPE
GDC-TR-CoreIP
ru-datafort-mnt