Skip to content

Hostname

retro.jp

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrant organisation
retro,inc.
Contact emails
proxy@whoisprotectservice.com, contact@retro.jp

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ns-245.awsdns-30.com
  • ns-785.awsdns-34.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
  • ns-1123.awsdns-12.org
  • ns-1988.awsdns-56.co.uk

MX records

  • retro-jp.mail.protection.outlook.com
  • zeelco.sakura.ne.jp
  • mx.sendgrid.net

SPF policy

  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: spf.bserver.jp
  • include: _spf.maildeliver.jp
  • include: spfgw.fsi.ne.jp
  • a: www619b.sakura.ne.jp
  • mx: retro.jp
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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