Skip to content

Hostname

recurrent.co.jp

Last fetched

recurrent.co.jp resolves to 203.174.70.208, announced in 203.174.64.0/20 by DATAHOTEL-JP - AS for DATAHOTEL, which is one of iDC in Japan, in JP. recurrent.co.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 · recurrent.co.jpRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/recurrent.co.jp

Resolution chain

IPv6 resolution

No AAAA record for recurrent.co.jp is recorded in WhisperGraph.

Attribution

nhn techorus

ORIGIN_AS

WHOIS identity

Registrant organisation
japan license bank

Subdomains

Subdomain
cad.recurrent.co.jp
corp.recurrent.co.jp
koushi.recurrent.co.jp
m.recurrent.co.jp
mezzalink.recurrent.co.jp
mezzanine.recurrent.co.jp
mezzanine09.recurrent.co.jp
ms.recurrent.co.jp
noel.recurrent.co.jp
page.recurrent.co.jp
s.recurrent.co.jp
storage.recurrent.co.jp

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

  • zns01.datahotel.ne.jp
  • zns02.datahotel.ne.jp

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: 153.127.52.19/32
  • ip: 203.174.70.193/26
  • include: _spf.google.com
  • mx: recurrent.co.jp
  • include: spf-bma.mpme.jp
  • include: sender.zcsend.jp
  • include: 3481558.spf08.hubspotemail.net

Threat-feed evidence

History

Related pages

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