Skip to content

Hostname

patientkeeper.com

Last fetched

patientkeeper.com resolves to 206.31.240.233, announced in 206.31.240.0/20 by CENTURYLINK-LEGACY-SAVVIS - CenturyLink Communications, LLC in US. patientkeeper.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 · patientkeeper.comRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/patientkeeper.com

Resolution chain

IPv6 resolution

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

Attribution

centurylink

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
c823a2e29hh@networksolutionsprivateregistration.com, cc67v93b76w@networksolutionsprivateregistration.com, d24hm2rj2jx@networksolutionsprivateregistration.com, d975r2tk2v4@networksolutionsprivateregistration.com, dj8m96y48tc@networksolutionsprivateregistration.com, ha2sz4cq7qc@networksolutionsprivateregistration.com, hy8b87s62z8@networksolutionsprivateregistration.com, n768v5qu5gb@networksolutionsprivateregistration.com, na33h2b28dy@networksolutionsprivateregistration.com, ph6d78g24cx@networksolutionsprivateregistration.com, pk8bj8r469p@networksolutionsprivateregistration.com, r87cc6rw4gy@networksolutionsprivateregistration.com, rm6m96wh6td@networksolutionsprivateregistration.com, t236g4y629n@networksolutionsprivateregistration.com, tf7xe6me8bm@networksolutionsprivateregistration.com, ua3r46xw2hs@networksolutionsprivateregistration.com, wd3mn5223q2@networksolutionsprivateregistration.com, x54a98498fb@networksolutionsprivateregistration.com, x753558685k@networksolutionsprivateregistration.com, xe6zv4du9sa@networksolutionsprivateregistration.com and 2 more

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

  • ns1.patientkeeper.com
  • ns2.patientkeeper.com
  • prd-ns01.patientkeeper.com
  • ns1.savvis.net
  • ns2.savvis.net
  • ns3.savvis.net
  • ns4.savvis.net
  • ns5.savvis.net

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

  • ip: 206.31.240.195/32
  • include: spf.mandrillapp.com
  • include: _spf1.patientkeeper.com
  • include: _spf.salesforce.com
  • ip: 128.136.255.100
  • ip: 208.76.139.108
  • ip: 209.190.168.101
  • ip: 209.190.168.105
  • ip: 209.190.168.29
  • ip: 209.190.168.98

Threat-feed evidence

History

Related pages

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