Hostname
invt.io
Last fetched
invt.io resolves to 18.203.3.80, announced in 18.202.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IE. invt.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.203.3.80
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.211.22.236
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.213.159.152
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.30.136.229
52.30.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.49.230.231
52.48.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.51.46.238
52.48.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.194.146.173
54.194.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.72.77.61
54.72.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.72.8.35
54.72.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.80.210.117
99.80.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.80.237.129
99.80.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for invt.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
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-510.awsdns-63.com
- ns-600.awsdns-11.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-1228.awsdns-25.org
- ns-1751.awsdns-26.co.uk
Threat-feed evidence
History
Related pages
Pivot from invt.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: "invt.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.