What counts as a routing conflict here?

A MOAS conflict, meaning more than one ASN announcing overlapping address space for the same prefix, which is the signature of both an accidental leak and a deliberate hijack.

Does a missing ROA always mean a hijack risk?

It means the network has no RPKI-signed authorization for that prefix, so a hijacker announcing it would not be automatically rejected by ROV-enforcing networks. It raises exposure; it does not by itself prove an attack is underway.

Can I check a specific prefix instead of a whole ASN?

No. This audit takes an ASN and checks a sample of the prefixes it announces. To profile one prefix, run the Network & Routing Report.

How current is the RPKI data?

It reads ROA state from the graph each time it runs.

Only in WhisperNetwork & BGP

Which domains would a BGP hijack actually expose?

Grade a network's routing security and trace conflicts to the domains they'd expose.

Try this in Console

No credit card needed.

What it solves

Routing-security tools usually stop at the network layer and report a MOAS conflict or a missing ROA as an abstract fact. Network and threat teams need to know what a hijack on this specific network would actually put at risk, meaning which domains and organisations sit on the exposed blocks, not just that a conflict exists.

It reads the ASN’s announced prefixes, finds any block with a routing conflict or a coverage gap in RPKI, then walks from the affected prefixes to the hostnames and organisations that resolve there, and rolls the findings into a routing-hygiene scorecard covering ROA expiry, over-permissive maxLength values and RIR trust anchors.

The old way3 tools / tabs

Checking routing hygiene and checking exposure are usually two separate exercises in two separate tools, and neither one tells you which domains would actually go dark or get hijacked.

a BGP looking glass
the RPKI validator dashboard for each RIR
manual DNS lookups on the affected blocks

What this means

Give it an ASN and it grades the network’s routing hygiene against the conflicts and RPKI gaps that make hijacking possible.
It traces any conflict to the actual domains and organisations hosted on the affected address blocks, crossing the BGP, RPKI and DNS layers.

Dig deeper

Key concepts

Read the how-to

What this workflow does and how it uses the graph, plus the copy-paste recipes it's built from.

Open the documentation

Why teams run this

The job this flow does, the failure mode it removes, and the proof it produces.

Security leaders

Related flows

All use cases

Only in Whisper

Network & Routing Report

The full picture of how a network is put together and reaches the internet. Give it a network or address block and get a health card: what it announces, who it peers and buys transit from, whether it leans dangerously on a single upstream, and how well its routes are protected. The one-look report for network engineers assessing reach and resilience.

Network & BGPDocs