MCT B.V.
MCT SAS
Data as of 2026-08-09
GLEIF verified
Complete entity footprint
2 linked clusters ·
21 netblocks ·
1,256 IPv4 addresses ·
2 IPv6 prefixes
This organisation's clusters combined by evidence —
shared GLEIF corporate family
— not name similarity, so genuinely different organisations that share a name are excluded.
LEI
724500U9X8PYYAY7IF17
Registered name
MCT B.V.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 10 · 1,064 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2a03:3c20::/32) |
| Registered in | France (6) · Germany (3) |
| Cluster ID | 218257697 |
| Registry | BGP |
| Owner jurisdiction | NL |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 724500U9X8PYYAY7IF17 |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
7 weekly snapshots · JSON
11
-11 netblocks since 2026-07-05
2026-07-05
peak 22
2026-08-09
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 85.115.26.48/29 | mct Datensysteme GmbH | RIPE | ASSIGNED PA | ● high |
| 85.115.26.240/28 | mct Datensysteme GmbH | RIPE | ASSIGNED PA | ● high |
| 185.72.4.0/24 | MCT SAS | BGP | ANNOUNCED | ● high |
| 185.72.5.0/24 | MCT SAS | BGP | ANNOUNCED | ● high |
| 185.72.6.0/24 | MCT SAS | BGP | ANNOUNCED | ● high |
| 185.72.7.0/24 | MCT SAS | BGP | ANNOUNCED | ● high |
| 213.144.8.64/28 | mct Datensysteme GmbH | RIPE | ASSIGNED PA | ● high |
| 2a02:788:10e:500::/56 | mct Datensysteme GmbH | RIPE | ASSIGNED | ● high |
| 185.72.4.0/22 | MCT SAS | RIPE | ALLOCATED PA | ● low |
| 2a03:3c20::/32 | MCT SAS | RIPE | ALLOCATED-BY-RIR | ● low |
IPv6 ranges (2)
Corporate group (2 confirmed entities)
+3 additional unconfirmed candidates not shown — full list (JSON)- MCT-LTD 11 blocks
Network trust
what's this?
RPKI hygiene: B
how networks compare →
81.8%
of checked blocks have valid RPKI ROA coverage
(9 of 11)
Possible discrepancies (1)
These blocks are registered to MCT SAS 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.
| 2a02:788:10e:500::/56 /56 | authorized for AS12843 — TelemaxX Telekommunikation GmbH |
NIC Handles
AS200906
DUMY-RIPE
DUMY-RIPE
MCT-MNT
MCT-MNT
ORG-MDG18-RIPE
ORG-NS224-RIPE
RIPE-NCC-HM-MNT
TXX-MNT