Hostname
on.tech
Last fetched
on.tech resolves to 108.138.26.16, announced in 108.138.24.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. on.tech 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.16
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.18
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.3
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.73
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.168.122.122
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.28
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.32
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.122.81
3.168.122.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 54.192.151.35
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.61
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.81
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.91
54.192.151.0/24 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
IPv6 resolution
No AAAA record for on.tech is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Mail and authentication
Nameservers
- ns-95.awsdns-11.com
- ns-953.awsdns-55.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-1063.awsdns-04.org
- ns-1556.awsdns-02.co.uk
MX records
- smtp.google.com
SPF policy
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from on.tech 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: "on.tech"})-[: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.