Hostname
2abet.org
Last fetched
2abet.org resolves to 13.227.192.121, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. 2abet.org 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.121
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.46
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.80
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.87
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.33.252.115
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.64
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.79
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.80
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.66.147.125
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.44
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.53
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.91
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.9.46.17
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.20
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.69
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.96
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
Subdomains
| Subdomain |
|---|
| www.2abet.org |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-493.awsdns-61.com
- ns-623.awsdns-13.net
- ns-1501.awsdns-59.org
- ns-1554.awsdns-02.co.uk
Threat-feed evidence
History
Related pages
Pivot from 2abet.org 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: "2abet.org"})-[: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.