Hostname
dafaexch.com
Last fetched
dafaexch.com resolves to 18.164.96.23, announced in 18.164.96.0/21 by AMAZON-02 - Amazon.com, Inc. in US. dafaexch.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.164.96.23
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.31
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.49
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.73
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.244.60.102
18.244.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 18.244.60.110
18.244.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 18.244.60.28
18.244.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 18.244.60.89
18.244.60.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 65.8.131.126
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.33
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.8
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.88
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.173.161.52
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.8
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.117
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.84
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- domains by proxy,
- Contact emails
- ddc67021318340ddb1e452006cc9ee35.protect@withheldforprivacy.com
Mail and authentication
Nameservers
- carioca.ns.cloudflare.com
- elliot.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from dafaexch.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: "dafaexch.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.