Infrastructure intelligence

The internet,
queryable like a database

DNS, routing, ownership, threat intel, even the physical datacenters — every layer of the internet, pre-joined into one live graph.Query it like a database: one question crosses every layer, with the history behind it and the evidence behind every verdict.

The value isn't the data. It's the connections.

Plenty of tools hand you a WHOIS record or a BGP route. Whisper pre-joins every layer of the internet, so one query crosses from a domain to the datacenter behind it — the traversal flat lookups can't reach.

The cross-layer pivot

One query crosses every layer

One domain, expanded across every layer the graph connects: the IPs it resolves to, the nameservers and mail servers behind it, who owns it, the network announcing its routes, the peers that network talks to, and the datacenters it physically sits in. Each connection is another question you can ask — so the graph isn’t a lookup, it’s a starting point.

DNSWebMailWHOISGeoIPRoutingPhysicalone query

This is one starting point. The same graph powers dozens of investigations — start from an alert, a domain, or a whole network.

Live · graph.whisper.security
One indicator, every connected layer
github.com expanded across DNS, web links, mail, ownership, GeoIP, routing, and the datacenters behind it
Domain · WebDNS · WHOIS · MailGeoIP · RoutingNetworkPeers · Physicalgithub.com34c3ctf.ccc.ac10xse.academyns-421.awsdns-52.c…ns-520.awsdns-01.n…dns1.p08.nsone.net140.82.121.3githubaspmx.l.google.comalt1.aspmx.l.googl…Frankfurt, DE140.82.121.0/24AS36459GitHub, Inc.AS1299AS2914AS3257Equinix AshburnEquinix Frankfurt
WebDNSMailWHOISGeoIPRoutingPhysical
Show the one query that built this
MATCH (h:HOSTNAME {name:"github.com"})-[:RESOLVES_TO]->(ip)
-[:ANNOUNCED_BY]->(:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
WITH h, a, ip LIMIT 1
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(c) // GeoIP
CALL { (h)<-[:NAMESERVER_FOR]-(ns) collect[0..3] }
CALL { (h)<-[:MAIL_FOR]-(mx) collect[0..2] }
CALL { (h)-[:REGISTERED_BY]->(o) collect[0..1] }
CALL { (h)-[:LINKS_TO]->(w) limit 2 }
CALL { (a)-[:PEERS_WITH]->(peer) collect[0..3] }
CALL { (a)-[:AS_PRESENT_AT]->(dc) collect[0..2] }
RETURN ip, prefix, asn, asn_name, geo, ns, mx, o, peer, dc
17 nodes across 7 layers · 201 msRun it
7.4B
nodes
0B
edges
0
threat feeds
0
entity types

Built for where the market is going

  • FCC submarine-cable security rules (2026)
  • EU €347M Cable Security Toolbox
  • NIS2 Art. 21 supply-chain risk
  • DORA Art. 28–30 concentration risk
  • RPKI now covers 60%+ of IPv4 prefixes
  • OWASP Top 10 for Agentic Apps (2025)

One graph. Three ways in.

Whisper is the infrastructure layer your stack queries when it needs context — over the API, through your SIEM, or straight from an AI agent.

Available as cloud-hosted or on-prem deployment.

Built by internet infrastructure experts

Few security companies can say they helped build the thing they protect. Whisper comes from people who did — engineers with time at RIPE NCC and ICANN, working on internet governance down at the protocol level. Meet the team.

We built Whisper because no tool gave us what we needed: one queryable map of how the internet actually connects. What used to take a research lab, any security team can now have.

W
Whisper Security Team
Internet infrastructure researchers
0+Years of experience

in internet infrastructure, DNS, BGP, PKI, and threat intelligence.

0BData points ingested

from 60+ internet data sources, cross-referenced and continuously updated.

0+Countries mapped

Global coverage across every IP range, ASN, and top-level domain.

Start seeing infrastructure

Connect Whisper once, and every tool in your stack gets sharper.