Skip to content

Hostname

mdconnection.com

Last fetched

mdconnection.com resolves to 100.27.58.25, announced in 100.42.56.0/23 by AMAZON-AES - Amazon.com, Inc. in US. mdconnection.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 · mdconnection.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/mdconnection.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
fa2va4sg8ur@networksolutionsprivateregistration.com, kz99h55m4uw@networksolutionsprivateregistration.com, sf9fa8s228u@networksolutionsprivateregistration.com, vm4p489q7pu@networksolutionsprivateregistration.com, xn2qw92n536@networksolutionsprivateregistration.com

Subdomains

Subdomain
bnickel.mdconnection.com
staging.mdconnection.com
www.mdconnection.com

Showing 3 of 3 subdomains (3 per page).

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-156.awsdns-19.com
  • ns-637.awsdns-15.net
  • ns-1409.awsdns-48.org
  • ns-1801.awsdns-33.co.uk

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

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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