Skip to content

Hostname

therapynotes.com

Last fetched

therapynotes.com resolves to 104.17.36.27, announced in 104.18.35.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. therapynotes.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 · therapynotes.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/therapynotes.com

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:440
Registrant organisation
brad pliner
Contact emails
ns@pliner.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • anna.ns.cloudflare.com
  • clint.ns.cloudflare.com
  • 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

MX records

  • therapynotes-com.mail.protection.outlook.com

SPF policy

  • include: helpscoutemail.com
  • include: spf.protection.outlook.com
  • a: therapynotes.com
  • mx: therapynotes.com
  • include: em4527.therapynotes.com
  • include: mail.zendesk.com
  • include: 2355828.spf03.hubspotemail.net
  • include: u826348.wl.sendgrid.net
  • include: u22842751.wl002.sendgrid.net
  • include: u395539.wl040.sendgrid.net

Threat-feed evidence

History

Related pages

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