Skip to content

Hostname

mydigiguide.com

Last fetched

mydigiguide.com resolves to 193.36.65.52, announced in 193.36.65.0/24 by PA-AS - The Press Association Limited in GB. mydigiguide.com 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 · mydigiguide.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/mydigiguide.com

Resolution chain

IPv6 resolution

No AAAA record for mydigiguide.com is recorded in WhisperGraph.

Attribution

press association

ORIGIN_AS

WHOIS identity

Registrar
iana:168
Registrant organisation
dan petitt
Contact emails
webmaster@gipsymedia.com, whoiscontact@names.co.uk

Subdomains

Subdomain
wap.mydigiguide.com
www.mydigiguide.com

Showing 2 of 2 subdomains (2 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

Mail and authentication

Nameservers

  • ns0.pa.press.net
  • ns1.pa.press.net
  • ns2.pa.press.net
  • ns3.pa.press.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

SPF policy

  • a: mydigiguide.com
  • mx: mydigiguide.com
  • a: mxa.rbsworldpay.com
  • a: mxa.worldpay.com
  • ip: 81.105.219.40
  • ip: 81.105.219.42
  • ip: 81.137.125.66
  • ip: 81.137.125.70
  • ip: 91.109.242.233
  • ip: 91.109.242.52
  • ip: 91.109.242.53

Threat-feed evidence

History

Related pages

Pivot from mydigiguide.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: "mydigiguide.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 20

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