Hostname
locize.io
Last fetched
locize.io resolves to 18.172.112.6, announced in 18.172.112.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. locize.io 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
- 18.172.112.6
18.172.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.172.112.64
18.172.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.172.112.9
18.172.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.172.112.97
18.172.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.239.208.29
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.37
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.64
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.208.84
18.239.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Brussels, BE
- 18.239.255.60
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.61
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.66
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.95
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
IPv6 resolution
No AAAA record for locize.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-439.awsdns-54.com
- ns-522.awsdns-01.net
- ns-1049.awsdns-03.org
- ns-1965.awsdns-53.co.uk
MX records
- mx1.mail.hostpoint.ch
- mx2.mail.hostpoint.ch
- inbound-smtp.eu-west-1.amazonaws.com
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from locize.io 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: "locize.io"})-[: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.