Hostname
fantheone.com
Last fetched
fantheone.com resolves to 3.169.231.101, announced in 3.169.228.0/22 by AMAZON-02 - Amazon.com, Inc. in US. fantheone.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
- 3.169.231.101
3.169.228.0/22 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.231.74
3.169.228.0/22 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.231.87
3.169.228.0/22 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.231.89
3.169.228.0/22 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 65.9.86.109
65.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 65.9.86.121
65.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 65.9.86.27
65.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 65.9.86.69
65.8.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for fantheone.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fantheone.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.
Subdomains
| Subdomain |
|---|
| admin-dev.fantheone.com |
| api.fantheone.com |
| app-dev.fantheone.com |
| app.fantheone.com |
| crew.fantheone.com |
Showing 5 of 5 subdomains (5 per page).
Mail and authentication
Nameservers
- ns-143.awsdns-17.com
- ns-875.awsdns-45.net
- ns-1170.awsdns-18.org
- ns-1633.awsdns-12.co.uk
MX records
- smtp.google.com
Threat-feed evidence
History
Related pages
Pivot from fantheone.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: "fantheone.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.