Skip to content

Hostname

edy.jp

Last fetched

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

Resolution chain

No IPv4 resolution is recorded for edy.jp in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrant organisation
rakuten edy,inc.
Contact emails
cwd-domain-admin@mail.rakuten.com, yoshito.naganuma@mail.rakuten.com, enami@bitwallet.co.jp

Subdomains

Subdomain
be.edy.jp
beext.edy.jp
beint.edy.jp
card.edy.jp
cp.edy.jp
cpn.edy.jp
dtv.edy.jp
dtvtestext.edy.jp
edypon.edy.jp
edyviewer.edy.jp
edyviewerext.edy.jp
edyviewerint.edy.jp

Showing 12 of 42. 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

  • ns01.rakuten.ad.jp
  • ns02.rakuten.ad.jp
  • ns.rakuten.co.jp
  • ns01.rakuten.co.jp
  • ns02.rakuten.co.jp
  • ns03.rakuten.co.jp
  • ns04.rakuten.co.jp
  • ns05.rakuten.co.jp
  • ns06.rakuten.co.jp

MX records

  • edy-jp.mail.eo.outlook.com
  • mg.drive.ne.jp

SPF policy

  • ip: 124.146.170.8/32
  • ip: 124.146.170.9/32
  • ip: 203.190.57.73
  • ip: 203.190.57.74
  • ip: 203.190.57.75
  • ip: 210.188.234.53
  • ip: 210.188.234.55

Threat-feed evidence

History

Related pages

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