Hostname
hitdanoigen.com
Last fetched
hitdanoigen.com resolves to 18.172.202.121, announced in 18.172.202.0/24 by AMAZON-02 - Amazon.com, Inc. in TH. hitdanoigen.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
- 18.172.202.121
18.172.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.172.202.16
18.172.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.172.202.89
18.172.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.172.202.90
18.172.202.0/24 · AMAZON-02 - Amazon.com, Inc. · Bangkok, TH
- 18.238.55.122
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.126
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.25
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.95
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for hitdanoigen.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
Mail and authentication
Nameservers
- ns-58.awsdns-07.com
- ns-658.awsdns-18.net
- 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
- ns-1440.awsdns-52.org
- ns-1601.awsdns-08.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: hitdanoigen.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from hitdanoigen.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: "hitdanoigen.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.