Hostname
webgears.at
Last fetched
webgears.at resolves to 18.238.80.114, announced in 18.238.80.0/23 by AMAZON-02 - Amazon.com, Inc. in US. webgears.at 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.238.80.114
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.15
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.45
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.63
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.41.61
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.65
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.73
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.95
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for webgears.at is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:hetzner online gmbh
- Registrant organisation
- tobias klien
- Contact emails
- kontakt@webgears.at
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
Sample outbound links
Mail and authentication
Nameservers
- ns-39.awsdns-04.com
- ns-1016.awsdns-63.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-1339.awsdns-39.org
- ns-1841.awsdns-38.co.uk
MX records
- webgears-at.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from webgears.at 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: "webgears.at"})-[: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.