Skip to content

Hostname

med-access.net

Last fetched

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

Resolution chain

No IPv4 resolution is recorded for med-access.net in WhisperGraph.

IPv6 resolution

No AAAA record for med-access.net is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Contact emails
med-access.net@domainprivacygroup.com, dns-owner@med-access.net, 439e0716-7163-4489-8d57-de635c135c42@identity-protect.org, 62cb041c-9a6d-472e-9cb1-80e55802b8eb@identity-protect.org, 6f628199-a1f5-4031-ac14-a363faafc2ef@identity-protect.org, a923a335-8bd5-40b7-8963-078bfb9e3406@identity-protect.org, e7d61ea5-ebbd-4656-9151-43d457f91215@identity-protect.org, eade954c-da89-4c52-a465-3c930b181f02@identity-protect.org, owner-4752453@med-access.net.whoisprivacyservice.org, owner-9657118@med-access.net.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-13.awsdns-01.com
  • ns-728.awsdns-27.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
  • ns-1140.awsdns-14.org
  • ns-1836.awsdns-37.co.uk

MX records

  • bliksem.nssi.telus.com
  • hagel.nssi.telus.com

SPF policy

  • ip: 208.87.196.2

Threat-feed evidence

History

Related pages

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