Hostname
polyglossia.io
Last fetched
polyglossia.io resolves to 13.32.121.111, announced in 13.32.120.0/23 by AMAZON-02 - Amazon.com, Inc. in DE. polyglossia.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
- 13.32.121.111
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.127
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.7
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.32.121.95
13.32.120.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 143.204.55.105
143.204.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Zurich, CH
- 143.204.55.20
143.204.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Zurich, CH
- 143.204.55.57
143.204.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Zurich, CH
- 143.204.55.90
143.204.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Zurich, CH
- 198.54.114.166
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
Subdomains
| Subdomain |
|---|
| app.polyglossia.io |
| www.polyglossia.io |
Showing 2 of 2 subdomains (2 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-191.awsdns-23.com
- dns1.namecheaphosting.com
- dns2.namecheaphosting.com
- ns-891.awsdns-47.net
- ns-1046.awsdns-02.org
- ns-1573.awsdns-04.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: spf.web-hosting.com
- ip: 198.54.114.40
- ip: 198.54.115.40
Threat-feed evidence
History
Related pages
Pivot from polyglossia.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: "polyglossia.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.