Hostname
33zkg.com
Last fetched
33zkg.com resolves to 13.226.244.112, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. 33zkg.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.226.244.112
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.20
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.41
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.226.244.94
13.226.244.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.227.192.108
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.27
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.38
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.9
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 3.166.135.100
3.166.128.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.135.15
3.166.128.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.135.60
3.166.128.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.135.68
3.166.128.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.170.229.100
3.170.229.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.170.229.12
3.170.229.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.170.229.61
3.170.229.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.170.229.85
3.170.229.0/24 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
IPv6 resolution
No AAAA record for 33zkg.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1923
Mail and authentication
Nameservers
- ns-127.awsdns-15.com
- ns-1002.awsdns-61.net
- ns-1399.awsdns-46.org
- ns-1975.awsdns-54.co.uk
Threat-feed evidence
History
Related pages
Pivot from 33zkg.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: "33zkg.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.