Hostname
help.cuckoo.co
Last fetched
help.cuckoo.co resolves to 108.138.51.100, announced in 108.138.48.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. help.cuckoo.co 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
- 108.138.51.100
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.45
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.56
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.82
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 3.166.96.112
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.123
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.29
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.98
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
IPv6 resolution
No AAAA record for help.cuckoo.co is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for help.cuckoo.co. 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.
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-463.awsdns-57.com
- ns-581.awsdns-08.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-1189.awsdns-20.org
- ns-1678.awsdns-17.co.uk
Threat-feed evidence
History
Related pages
Pivot from help.cuckoo.co 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: "help.cuckoo.co"})-[: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.