Skip to content

Hostname

mymd.jp

Last fetched

mymd.jp resolves to 203.183.165.150, announced in 203.183.160.0/19 by IDCF - IDC Frontier Inc. in JP. mymd.jp 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 · mymd.jpRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.6/10canon.whisper.security/host/mymd.jp

Resolution chain

IPv6 resolution

No AAAA record for mymd.jp is recorded in WhisperGraph.

Attribution

idc frontier

ORIGIN_AS

WHOIS identity

Registrant organisation
yamada denki
Contact emails
support@netsurf.ad.jp, ysuzuki@yamada-denki.jp

Subdomains

Subdomain
api.mymd.jp
api2.mymd.jp
au.mymd.jp
best.mymd.jp
cbc.mymd.jp
cdn-origin.mymd.jp
cdn.mymd.jp
cdn2.mymd.jp
dg.mymd.jp
dgs.mymd.jp
ebook.mymd.jp
gpf-admin.mymd.jp

Showing 12 of 137. View all subdomains →

Mail and authentication

Nameservers

  • ns020-2cbg39sk0f1pa602.2.d-53.info
  • dns-b.iij.ad.jp
  • dns-c.iij.ad.jp
  • ns020-2cbg39sk0f1pa602.2.d-53.jp
  • ns020-2cbg39sk0f1pa602.2.d-53.net
  • ns000.d-53.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

MX records

  • mail.tpgaw.jp

SPF policy

  • ip: 203.183.165.128/25
  • ip: 202.55.138.218/31
  • ip: 202.55.138.220/30
  • ip: 202.55.138.224/28
  • ip: 202.55.138.240/29

Threat-feed evidence

History

Related pages

Pivot from mymd.jp 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: "mymd.jp"})-[: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.