Hostname
www.digify.com
Last fetched
www.digify.com resolves to 13.33.187.110, announced in 13.33.159.0/24 by AMAZON-02 - Amazon.com, Inc. in DE. www.digify.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
- 13.33.187.110
13.33.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.13
13.33.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.18
13.33.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.29
13.33.159.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.164.13.121
18.161.249.0/24 · AMAZON-02 - Amazon.com, Inc. · Lima, PE
- 18.164.13.127
18.161.249.0/24 · AMAZON-02 - Amazon.com, Inc. · Lima, PE
- 18.164.13.46
18.161.249.0/24 · AMAZON-02 - Amazon.com, Inc. · Lima, PE
- 18.164.13.88
18.161.249.0/24 · AMAZON-02 - Amazon.com, Inc. · Lima, PE
IPv6 resolution
No AAAA record for www.digify.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for www.digify.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.
Mail and authentication
Nameservers
- ns-64.awsdns-08.com
- ns-987.awsdns-59.net
- ns-1186.awsdns-20.org
- ns-1864.awsdns-41.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- ip: 103.25.52.0/24
- ip: 203.174.87.0/24
- include: amazonses.com
- a: www.digify.com
- mx: www.digify.com
- include: _spf.google.com
- include: spf.mandrillapp.com
- include: spf.mail.intercom.io
- include: 43789292.spf10.hubspotemail.net
- ip: 209.85.210.45
Threat-feed evidence
History
Related pages
Pivot from www.digify.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: "www.digify.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.