Hostname
numeral.io
Last fetched
numeral.io resolves to 108.138.26.64, announced in 108.138.24.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. numeral.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
- 108.138.26.64
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.72
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.85
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.9
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.67.13.16
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.17
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.60
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.67.13.14
18.67.12.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
IPv6 resolution
No AAAA record for numeral.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-237.awsdns-29.com
- ns-560.awsdns-06.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1472.awsdns-56.org
- ns-1714.awsdns-22.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
- zcbhwtqqo24kjk7u2edlvlmfrdhyghnvq2zt57xbhw7fjr74hvta.mx-verification.google.com
SPF policy
- include: _spf.google.com
- include: 25739848.spf07.hubspotemail.net
Threat-feed evidence
History
Related pages
Pivot from numeral.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: "numeral.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.