Hostname
nic.hot
Last fetched
nic.hot resolves to 15.197.172.231, announced in 15.197.160.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. nic.hot 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
- 15.197.172.231
15.197.160.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 3.33.179.131
3.33.176.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
IPv6 resolution
IPv6 resolution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Attribution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
WHOIS identity
- Registrar
- iana:9999
- Registrant organisation
- amazon registry services,
Subdomains
Subdomains is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Mail and authentication
Nameservers
- dns1.nic.hot
- dns2.nic.hot
- dns3.nic.hot
- dns4.nic.hot
- dnsa.nic.hot
- dnsb.nic.hot
- dnsc.nic.hot
- dnsd.nic.hot
- 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 nic.hot 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: "nic.hot"})-[: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.