Hostname
digybot.io
Last fetched
digybot.io resolves to 13.35.37.2, announced in 13.35.37.0/24 by AMAZON-02 - Amazon.com, Inc. in SG. digybot.io 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
- 13.35.37.2
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.36
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.5
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.35.37.92
13.35.37.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.160.150.106
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.21
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.55
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.160.150.87
3.160.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for digybot.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:81
Subdomains
Showing 11 of 11 subdomains (11 per page).
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-278.awsdns-34.com
- ns-940.awsdns-53.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-1521.awsdns-62.org
- ns-1676.awsdns-17.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
Threat-feed evidence
History
Related pages
Pivot from digybot.io 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: "digybot.io"})-[: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.