Hostname
api.getsupernatural.com
Last fetched
api.getsupernatural.com resolves to 100.22.232.56, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. api.getsupernatural.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 100.22.232.56
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 16.146.128.56
16.146.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 35.166.70.230
35.160.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.224.185.145
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.36.162.118
52.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.43.28.25
52.40.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.149.83.199
54.148.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.213.61.120
54.213.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for api.getsupernatural.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.getsupernatural.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
Threat-feed evidence
History
Related pages
Pivot from api.getsupernatural.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: "api.getsupernatural.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.