Skip to content

Hostname

colopl.jp

Last fetched

colopl.jp resolves to 35.186.240.52, announced in 35.186.0.0/16 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. colopl.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 · colopl.jpRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.8/10canon.whisper.security/host/colopl.jp

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · DNS_OPERATOR, ORIGIN_AS

WHOIS identity

Registrant organisation
colopl,
Contact emails
domain@colopl.co.jp, whoisguard@do-reg.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

  • colopl.jp
  • a1-248.akam.net
  • a12-67.akam.net
  • a22-64.akam.net
  • a24-65.akam.net
  • a5-66.akam.net
  • a7-67.akam.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

MX records

  • mx01.colopl.jp
  • mx02.colopl.jp
  • mx03.colopl.jp
  • mx04.colopl.jp

SPF policy

  • include: amazonses.com
  • include: spf01.colopl.jp
  • include: spf02.colopl.jp
  • include: mdmessi.maildealer.jp
  • include: spf.mptx.jp
  • include: spf.repica.jp

Threat-feed evidence

History

Related pages

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