Skip to content

Hostname

medpeer.jp

Last fetched

medpeer.jp resolves to 13.227.192.114, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. medpeer.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 · medpeer.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/medpeer.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
paperboy&co.
Contact emails
admin@muumuu-domain.com, 08fbb36e42a20f03e4243c0264c7b1e9-46465940@contact.gandi.net

Subdomains

Subdomain
assets.medpeer.jp
career-admin-v2.medpeer.jp
career-customer.medpeer.jp
career-v2.medpeer.jp
career.medpeer.jp
cdn.medpeer.jp
clinic.medpeer.jp
id.medpeer.jp
jp-stg-mailsend01.medpeer.jp
kakari-api.medpeer.jp
kakari-blog.medpeer.jp
kakari-pharmacy-support.medpeer.jp

Showing 12 of 32. View all subdomains →

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-60.awsdns-07.com
  • ns-787.awsdns-34.net
  • ns-1274.awsdns-31.org
  • ns-1976.awsdns-55.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

  • ip: 35.74.60.121/32
  • ip: 54.178.115.154/32
  • ip: 35.75.71.172/32
  • ip: 35.76.228.216/32
  • ip: 54.95.41.32/32
  • ip: 35.73.48.7/32
  • include: amazonses.com
  • include: _spf.google.com
  • include: asp.cuenote.jp
  • include: spf-bma.mpme.jp
  • include: spf.repica.jp

Threat-feed evidence

History

Related pages

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