Hostname
e-digital.global
Last fetched
e-digital.global resolves to 108.138.26.125, announced in 108.138.24.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. e-digital.global 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.125
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.129
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.82
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 108.138.26.96
108.138.24.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.155.202.42
18.155.200.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.155.202.65
18.155.200.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.155.202.73
18.155.200.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.155.202.78
18.155.200.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.244.146.62
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.69
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.72
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.91
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
IPv6 resolution
No AAAA record for e-digital.global is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1086
Subdomains
Showing 12 of 17. View all subdomains →
Mail and authentication
Nameservers
- ns-87.awsdns-10.com
- ns-761.awsdns-31.net
- ns-1388.awsdns-45.org
- ns-1681.awsdns-18.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: mail.zendesk.com
- include: 8845911.spf05.hubspotemail.net
Threat-feed evidence
History
Related pages
Pivot from e-digital.global 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: "e-digital.global"})-[: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.