Skip to content

Hostname

medcor.com

Last fetched

medcor.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. medcor.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 · medcor.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/medcor.com

Resolution chain

No IPv4 resolution is recorded for medcor.com in WhisperGraph.

IPv6 resolution

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
07de84a80a28fd0a234f18c70ac7e078@domaindiscreet.com, 0f7e92e10a28fd0a0724dd30be1e2e5f@domaindiscreet.com, 3b115d380a28fd0a155e9af2a443181d@domaindiscreet.com, 5046bc3c0a28fd0a08a1a5ba6655831f@domaindiscreet.com, 52ofi2dbl0hcm8b4sq410deq6r@domaindiscreet.com, 8d9e0a4c0a28fd0a6af46720c4696df9@domaindiscreet.com, dd07e8a60a28fd0a27e1c4c3456e28c3@domaindiscreet.com, tim@medcor.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

  • ns65.domaincontrol.com
  • ns66.domaincontrol.com

MX records

  • d259059a.ess.barracudanetworks.com
  • d259059b.ess.barracudanetworks.com

SPF policy

  • ip: 68.21.221.0/24
  • ip: 52.71.30.102/32
  • ip: 24.220.45.142/32
  • ip: 50.206.83.144/29
  • ip: 149.72.95.149/32
  • ip: 96.2.240.160/27
  • ip: 50.206.83.160/27
  • ip: 166.78.71.191/32
  • ip: 64.77.109.192/32
  • ip: 198.2.136.202/32
  • include: _spf-2.medcor.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: 8096135.spf01.hubspotemail.net

Threat-feed evidence

History

Related pages

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