Skip to content
Install MCP

Hostname

pymedns.net

Last fetched

pymedns.net resolves to 186.64.112.77, announced in 186.64.112.0/24 by AS52368 - ZAM LTDA. in CL. pymedns.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 · pymedns.netRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/pymedns.net

Resolution chain

IPv6 resolution

No AAAA record for pymedns.net is recorded in WhisperGraph.

Attribution

zam ltda

DNS_OPERATOR, ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
chan feng
Contact emails
monitoreo@zamltda.com, san@haulmer.com, contact@privacyprotect.org

Subdomains

Subdomain
220-pyme85.pymedns.net
_spf.pymedns.net
cx201rk03sx01-pyme03.pymedns.net
mx1.pymedns.net
nds1.pymedns.net
ns.pymedns.net
ns1.pymedns.net
ns2.pymedns.net
ns3.pymedns.net
ns4.pymedns.net
nsl.pymedns.net
pyme0.pymedns.net

Showing 12 of 792. View all subdomains →

Mail and authentication

Nameservers

  • ns1.pymedns.net
  • ns2.pymedns.net
  • ns3.pymedns.net

MX records

  • mail.haulmer.net
  • mail2.haulmer.net

Threat-feed evidence

History

Related pages

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