Hostname
ge4712.com
Last fetched
ge4712.com resolves to 13.227.192.118, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. ge4712.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.118
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.12
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.62
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.76
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 3.171.214.110
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.40
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.89
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.214.92
3.171.212.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.215.66
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.76
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.8
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.88
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for ge4712.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of ge4712.com owner
- Contact emails
- 172734e8-320e-492e-bf1f-30f3239428c9@identity-protect.org, 5e9272db-6afb-49b0-99c7-ef802187cee5@identity-protect.org
Subdomains
| Subdomain |
|---|
| wol.ge4712.com |
| www.ge4712.com |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-209.awsdns-26.com
- ns-951.awsdns-54.net
- ns-1091.awsdns-08.org
- ns-1696.awsdns-20.co.uk
Threat-feed evidence
History
Related pages
Pivot from ge4712.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: "ge4712.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.