Skip to content

Hostname

digitaldruid.net

Last fetched

digitaldruid.net resolves to 109.74.203.238, announced in 109.74.192.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. digitaldruid.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · digitaldruid.netRouting diversity1.5/10Peering density6.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/digitaldruid.net

Resolution chain

IPv6 resolution

Attribution

akamai

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:472
Registrant organisation
dynadot privacy service
Contact emails
6fd529ce2bf04852a82968810d8f01f6.protect@whoisguard.com, mdesantis@gmx.net

Subdomains

Subdomain
counter.digitaldruid.net
ftp.digitaldruid.net
mail.digitaldruid.net
mail2.digitaldruid.net
ns1.digitaldruid.net
ns2.digitaldruid.net
reseller.digitaldruid.net
www.digitaldruid.net

Showing 8 of 8 subdomains (8 per page).

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

  • ns1.linode.com
  • ns2.linode.com
  • ns3.linode.com
  • ns4.linode.com
  • ns5.linode.com

MX records

  • mail.digitaldruid.net

SPF policy

  • a: journeylodge.com
  • mx: journeylodge.com
  • a: digitaldruid.net
  • mx: digitaldruid.net
  • a: mail.digitaldruid.net
  • a: mail2.digitaldruid.net
  • ip: 0:0:0:0:0:ffff:5850:bc6f
  • ip: 109.74.203.238
  • ip: 139.162.201.250
  • ip: 139.162.242.204
  • ip: 178.79.141.246
  • ip: 2a01:7e00:0:0:f03c:91ff:fe7a:e92c
  • ip: 2a01:7e00:0:0:f03c:91ff:fe93:6d11
  • ip: 88.80.188.111

Threat-feed evidence

History

Related pages

Pivot from digitaldruid.net 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: "digitaldruid.net"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.