Skip to content

Hostname

twinmed.com

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of twinmed.com owner
Contact emails
domain-admin@twinmed.com, 3138a80c-deef-44ee-bd62-f517ea2e620f@identity-protect.org, 4c14d3d7-b33f-4abd-9c9d-50d521b2ba86@identity-protect.org, 6cb14abe-a83e-40c2-8e13-5e06086eb744@identity-protect.org, 96eac45f-d89b-439e-8b5b-f83394469575@identity-protect.org, 9acbfbbb-e21d-4ecd-af1d-b649e7968cd3@identity-protect.org, db22cec3-62ae-4a9a-9f0d-558fe8fd1627@identity-protect.org, owner-10368889@twinmed.com.whoisprivacyservice.org, owner-10836220@twinmed.com.whoisprivacyservice.org, owner-6231678@twinmed.com.whoisprivacyservice.org, owner-8343346@twinmed.com.whoisprivacyservice.org

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

  • ns-314.awsdns-39.com
  • ns-923.awsdns-51.net
  • ns-1179.awsdns-19.org
  • ns-1544.awsdns-01.co.uk

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: _netblocks.mimecast.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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