Routing security

AS43362 MAJORDOMO

Unclassified ARIN

RPKI valid 83% 15 of 18 announcements

RPKI invalid 0 none

No ROA 3 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 19 authorising this AS

Announcements

What this network originates

18 observed

Every prefix observed with AS43362 as its origin, checked against RPKI and the IRR. Problems sort first.

Prefix	RPKI	IRR	Vantage points
78.108.81.0/24	No ROA	IRR	54
78.108.84.0/23	No ROA	IRR	54
185.84.110.0/23	No ROA	IRR	54
37.153.64.0/23	RPKI valid	IRR covering	54
37.153.70.0/24	RPKI valid	IRR	54
78.108.80.0/24	RPKI valid	IRR	54
78.108.82.0/23	RPKI valid	IRR	54
78.108.86.0/23	RPKI valid	IRR	54
78.108.88.0/23	RPKI valid	IRR	54
78.108.90.0/23	RPKI valid	IRR	54
78.108.92.0/23	RPKI valid	IRR	54
78.108.94.0/23	RPKI valid	IRR	54
130.49.174.0/24	RPKI valid	IRR	54
178.250.241.0/24	RPKI valid	IRR	53
178.250.242.0/23	RPKI valid	IRR	54
178.250.244.0/23	RPKI valid	IRR	54
178.250.246.0/23	RPKI valid	IRR	54
185.84.108.0/23	RPKI valid	IRR	54

RPKI · ROAs

Route origin authorisations

19 ROAs

Signed statements by address holders that AS43362 may originate these prefixes, up to the maximum length shown.

Prefix	Max length	Trust anchor
37.153.64.0/22	/22	RIPENCC
37.153.64.0/23	/23	RIPENCC
37.153.68.0/23	/23	RIPENCC
37.153.70.0/23	/23	RIPENCC
37.153.70.0/24	/24	RIPENCC
78.108.80.0/24	/24	RIPENCC
78.108.82.0/23	/23	RIPENCC
78.108.86.0/23	/23	RIPENCC
78.108.88.0/23	/23	RIPENCC
78.108.90.0/23	/23	RIPENCC
78.108.92.0/23	/23	RIPENCC
78.108.94.0/23	/23	RIPENCC
130.49.174.0/24	/24	RIPENCC
178.250.240.0/21	/24	RIPENCC
178.250.240.0/23	/23	RIPENCC
178.250.242.0/23	/23	RIPENCC
178.250.244.0/23	/23	RIPENCC
178.250.246.0/23	/23	RIPENCC
185.84.108.0/23	/23	RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

29 objects · 12 not announced

Route objects naming AS43362 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

Prefix	Source	Description	Maintainer	Changed	Routing
37.153.64.0/22	RIPE	—	`WEBA-SETI-MNT`	2026-06-06	Not announced
37.153.68.0/23	RIPE	—	`WEBA-SETI-MNT`	2026-06-06	Not announced
78.108.86.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2011-03-10	Not announced
78.108.87.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2011-03-10	Not announced
78.108.88.0/21	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Not announced
178.250.240.0/22	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Not announced
178.250.240.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Not announced
178.250.240.0/24	RIPE	—	`MNT-MAJORDOMO`	2026-10-13	Not announced
178.250.244.0/22	RIPE	Saint-Petersburg department Majordomo Llc	`MNT-MAJORDOMO`	2013-08-14	Not announced
178.250.244.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2011-03-10	Not announced
178.250.245.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2011-03-10	Not announced
2a02:dac0:f1f0::/48	RIPE	—	`MNT-MAJORDOMO`	2021-12-08	Not announced
37.153.70.0/24	RIPE	—	`WEBA-SETI-MNT`	2026-06-06	Announced
78.108.80.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2010-09-17	Announced
78.108.81.0/24	RIPE	Majordomo network	`MNT-MAJORDOMO`	2007-08-08	Announced
78.108.82.0/23	RIPE	Majordomo network	`MNT-MAJORDOMO`	2007-08-08	Announced
78.108.84.0/23	RIPE	Majordomo network	`MNT-MAJORDOMO`	2007-08-08	Announced
78.108.86.0/23	RIPE	Majordomo network	`MNT-MAJORDOMO`	2010-09-17	Announced
78.108.88.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Announced
78.108.90.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Announced
78.108.92.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Announced
78.108.94.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Announced
130.49.174.0/24	RIPE	—	`IHC-MNT`	2026-01-21	Announced
178.250.241.0/24	RIPE	—	`MNT-MAJORDOMO`	2026-10-13	Announced
178.250.242.0/23	RIPE	Majordomo route object	`MNT-MAJORDOMO`	2015-12-02	Announced
178.250.244.0/23	RIPE	Saint-Petersburg department Majordomo Llc	`MNT-MAJORDOMO`	2010-09-13	Announced
178.250.246.0/23	RIPE	Majordomo Network	`MNT-MAJORDOMO`	2012-10-29	Announced
185.84.108.0/23	RIPE	Majordomo network	`MNT-MAJORDOMO`	2015-12-23	Announced
185.84.110.0/23	RIPE	Nethouse network	`MNT-MAJORDOMO`	2015-12-23	Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS43362 directly show who expects to carry it.

AS-set	Where	Relationship
`AS-CITYTELECOM-DDOS`	RIPE	Lists AS43362 as a direct member
`AS-DATAIX`	RIPE	Lists AS43362 as a direct member
`AS-MASTERTEL`	RIPE	Lists AS43362 as a direct member
`AS-MSKROUTESERVER`	RIPE	Lists AS43362 as a direct member
`AS-PIRIX`	RIPE	Lists AS43362 as a direct member
`AS-PROMETEY`	RIPE	Lists AS43362 as a direct member
`AS-RETN-ACTUAL-V4`	RIPE	Lists AS43362 as a direct member
`AS-SERVICEPIPE`	RIPE	Lists AS43362 as a direct member
`AS-TRANSROUTE-SPEC`	RIPE	Lists AS43362 as a direct member
`AS-WEBA`	RIPE	Lists AS43362 as a direct member

RPKI from rpki-client, validated 2026-10-15 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-15. Cross-check on bgp.he.net.