INTRACON CORP.
INTRACON-LTD
Data as of 2026-09-20
GLEIF verified
Limited data: only 2 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.
LEI
549300H9UBM3XZKHJE65
Registered name
INTRACON CORP.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
This organisation
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2a00:2381:bbd::/48) |
| Record ID | 243329723 |
| Registry | RIPE |
| Owner jurisdiction | US-CT |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 549300H9UBM3XZKHJE65 |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 194.244.41.64/27 | INTRACON-NET | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:bbd::/48 | INTRACON-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a00:2381:bbd::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to INTRACON-LTD 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.
| 2a00:2381:bbd::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AS3302-MNT
BTNET-MNT
DUMY-RIPE
DUMY-RIPE