Skip to content

Hostname

concent.co.jp

Last fetched

concent.co.jp resolves to 133.242.253.90, announced in 133.242.0.0/16 by SAKURA-A - SAKURA Internet Inc. in JP. concent.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 · concent.co.jpRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.0/10canon.whisper.security/host/concent.co.jp

Resolution chain

IPv6 resolution

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

Attribution

sakura

ORIGIN_AS

WHOIS identity

Registrant organisation
concent corporation

Subdomains

Subdomain
app.concent.co.jp
biznet.concent.co.jp
cftest.concent.co.jp
faq.concent.co.jp
ftp.concent.co.jp
hub.concent.co.jp
messagecard.concent.co.jp
note.concent.co.jp
oexcmv.concent.co.jp
www.concent.co.jp

Showing 10 of 10 subdomains (10 per page).

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

  • master.dns.ne.jp
  • ns1.dns.ne.jp
  • ns2.dns.ne.jp

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • a: ghs.google.com
  • include: spf.google.com
  • a: www.concent.co.jp
  • include: spf.haihaimail.jp
  • include: spf.repica.jp
  • include: rtg.snva.jp
  • include: 243154654.spf07.hubspotemail.net
  • ip: 118.27.107.170
  • ip: 133.242.253.84
  • ip: 133.242.253.90
  • ip: 160.251.80.173

Threat-feed evidence

History

Related pages

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