Hostname
dy01b.com
Last fetched
dy01b.com resolves to 13.227.192.105, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. dy01b.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
- 13.227.192.105
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.24
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.69
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.74
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.32.121.104
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.107
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.76
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.93
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.67.12
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.61
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.75
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.85
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.239.199.103
18.239.196.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.239.199.65
18.239.196.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.239.199.66
18.239.196.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.239.199.82
18.239.196.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
IPv6 resolution
No AAAA record for dy01b.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
Mail and authentication
Nameservers
- ns-243.awsdns-30.com
- ns-806.awsdns-36.net
- ns-1231.awsdns-25.org
- ns-1725.awsdns-23.co.uk
Threat-feed evidence
History
Related pages
Pivot from dy01b.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: "dy01b.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.