Vejen-net Forening
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 1,278 IPv4 addresses |
| Cluster ID | 210342727 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.157.116.0/22 | Vejen-net Forening | RIPE | ALLOCATED PA | ● low |
| 195.249.143.0/24 | VEJEN-NET | RIPE | ASSIGNED PA | ● low |
| 2a07:a680::/29 | Vejen-net Forening | RIPE | ALLOCATED-BY-RIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to Vejen-net Forening 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.
| 195.249.143.0/24 /24 | authorized for AS3292 — TDC Holding A/S |
NIC Handles
AS3292-MNT
ASOM-NET-MNT
DUMY-RIPE
DUMY-RIPE
ORG-AV31-RIPE
RIPE-NCC-HM-MNT