Hostname
ebedge.com
Last fetched
ebedge.com resolves to 108.138.51.101, announced in 108.138.48.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. ebedge.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
- 108.138.51.101
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.110
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.78
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.138.51.8
108.138.48.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.84.160.10
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.14
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.32
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.51
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for ebedge.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:3786
- Registrant organisation
- gamestop hostmaster
- Contact emails
- hostmaster@gamestop.com
Subdomains
| Subdomain |
|---|
| wildcard.ebedge.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-65.awsdns-08.com
- ns-870.awsdns-44.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-1518.awsdns-61.org
- ns-1868.awsdns-41.co.uk
Threat-feed evidence
History
Related pages
Pivot from ebedge.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: "ebedge.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.