Hostname
birlaexch.org
Last fetched
birlaexch.org resolves to 13.227.192.108, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. birlaexch.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.108
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.19
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.66
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.79
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 3.174.46.12
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.43
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.50
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.79
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.86.240.100
99.86.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Hamburg, DE
- 99.86.240.112
99.86.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Hamburg, DE
- 99.86.240.123
99.86.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Hamburg, DE
- 99.86.240.18
99.86.240.0/21 · AMAZON-02 - Amazon.com, Inc. · Hamburg, DE
- 99.86.253.39
99.86.253.0/24 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 99.86.253.76
99.86.253.0/24 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 99.86.253.29
99.86.253.0/24 · AMAZON-02 - Amazon.com, Inc. · London, GB
- 99.86.253.91
99.86.253.0/24 · AMAZON-02 - Amazon.com, Inc. · London, GB
IPv6 resolution
No AAAA record for birlaexch.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
Mail and authentication
Nameservers
- ns-128.awsdns-16.com
- ns1.dns-parking.com
- ns2.dns-parking.com
- ns-957.awsdns-55.net
- ns-1251.awsdns-28.org
- ns-1781.awsdns-30.co.uk
Threat-feed evidence
History
Related pages
Pivot from birlaexch.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: "birlaexch.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.