Skip to content

Hostname

routingapi.com

Last fetched

routingapi.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. routingapi.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · routingapi.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/routingapi.com

Resolution chain

No IPv4 resolution is recorded for routingapi.com in WhisperGraph.

IPv6 resolution

No AAAA record for routingapi.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:228
Registrant organisation
moniker privacy services
Contact emails
03e0a85e2782e2dc5fae43ca24a8c5f267ef60d1b5aa515cac7e73acccfa337b@routingapi.com.whoisproxy.org, 10a8a641c13fe5f6ed16982cabc4bdda83bdca5fc7cd0eaad1117705bd440078@routingapi.com.whoisproxy.org, 430170d70a5774344c83a84963199bf4b905560c1a29e5ed24150509cde40093@routingapi.com.whoisproxy.org, 48956fcd6003957bbccde8f46c3c69c0831f006a5092d64bf59b1661673ba8a5@routingapi.com.whoisproxy.org, 511af874a3ccdf210a5c43014fc25d5bd1b3640e5e8976007d3374a40c5e1c98@routingapi.com.whoisproxy.org, 61ce2f538b46fbe69a5151eeaba7a93ae1d0e0a9891a892d44eab3f52c20054f@routingapi.com.whoisproxy.org, 70a4ad5fc319c5bf9ec301a208355dd5bac5f2a015ea591a502a0f035b33a204@routingapi.com.whoisproxy.org, 711145d6ceae6064420029a8c59790e36f1785c0105385073484ce4e665539b1@routingapi.com.whoisproxy.org, 7aafebe1d29efccf4ce4d7a73c83da08da2223af045f3562e4a2f6670e79e6e2@routingapi.com.whoisproxy.org, 80e2f7df89d021ea250f3825545782ded21e87efc0b21b26d2fe7a2221a8f4f7@routingapi.com.whoisproxy.org, 9b8c070b35cc5bd6a325128f489cfb1f24f6e3e9aa385d011cee74f6ee280b6a@routingapi.com.whoisproxy.org, b9d0193211bc56e1e9def0f1ffed8f406a09232c6972f65d211e7def94d7d636@routingapi.com.whoisproxy.org, bd13b3c42dadec06e413c8b3623563c307c92946b151d1a06a60e5f4756c0ae3@routingapi.com.whoisproxy.org, bedcb30cbe809cb07fcd7c7598c59a328803b8681c3828a5c6cc51863a7ea58c@routingapi.com.whoisproxy.org, c597165f1e891cce645f20edd93d4d5edd8dbbc097d559778cd4c002643bd41e@routingapi.com.whoisproxy.org, d3ab790a1d5ec8aa5e64c7f46d39d867368d5fafd0e65f49b0820a45f0751119@routingapi.com.whoisproxy.org, f3c496cbfbb123b0af8d72c5676e0fbc806fa8b338a172b79b5e6016366dc6db@routingapi.com.whoisproxy.org

Subdomains

Subdomain
api.routingapi.com
dist.routingapi.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns-274.awsdns-34.com
  • ns-954.awsdns-55.net
  • ns-1174.awsdns-18.org
  • ns-1817.awsdns-35.co.uk

MX records

  • smtp.google.com

Threat-feed evidence

History

Related pages

Pivot from routingapi.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "routingapi.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.