Hostname
f1682.cc
Last fetched
f1682.cc resolves to 3.165.50.108, announced in 3.165.50.0/24 by AMAZON-02 - Amazon.com, Inc. in VN. f1682.cc 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.165.50.108
3.165.50.0/24 · AMAZON-02 - Amazon.com, Inc. · Ho Chi Minh City, VN
- 3.165.50.51
3.165.50.0/24 · AMAZON-02 - Amazon.com, Inc. · Ho Chi Minh City, VN
- 3.165.50.63
3.165.50.0/24 · AMAZON-02 - Amazon.com, Inc. · Ho Chi Minh City, VN
- 3.165.50.84
3.165.50.0/24 · AMAZON-02 - Amazon.com, Inc. · Ho Chi Minh City, VN
- 54.192.151.122
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.54
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.81
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.94
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
IPv6 resolution
No AAAA record for f1682.cc is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for f1682.cc. 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 |
|---|
| m.f1682.cc |
| www.f1682.cc |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-442.awsdns-55.com
- ns-945.awsdns-54.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-1248.awsdns-28.org
- ns-1572.awsdns-04.co.uk
Threat-feed evidence
History
Related pages
Pivot from f1682.cc 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: "f1682.cc"})-[: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.