Hostname
api.w3-edge.com
Last fetched
api.w3-edge.com resolves to 18.239.255.33, announced in 18.239.252.0/22 by AMAZON-02 - Amazon.com, Inc. in HU. api.w3-edge.com 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.239.255.33
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.43
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.88
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 18.239.255.92
18.239.252.0/22 · AMAZON-02 - Amazon.com, Inc. · Budapest, HU
- 3.160.170.45
3.160.170.0/24 · AMAZON-02 - Amazon.com, Inc. · Johannesburg, ZA
- 3.160.170.76
3.160.170.0/24 · AMAZON-02 - Amazon.com, Inc. · Johannesburg, ZA
- 3.160.170.90
3.160.170.0/24 · AMAZON-02 - Amazon.com, Inc. · Johannesburg, ZA
- 3.160.170.99
3.160.170.0/24 · AMAZON-02 - Amazon.com, Inc. · Johannesburg, ZA
IPv6 resolution
No AAAA record for api.w3-edge.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.w3-edge.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
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-381.awsdns-47.com
- ns-892.awsdns-47.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-1230.awsdns-25.org
- ns-1950.awsdns-51.co.uk
Threat-feed evidence
History
Related pages
Pivot from api.w3-edge.com 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: "api.w3-edge.com"})-[: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.