CONTINUOUS INTERNET TELEMETRY24H DRIFT950 material changesacross 853 domains · +496 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination parity.domains · +20 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination pphosted.com · +4 vs yesterdayNOW2,719 curated domains not answering+504 vs yesterdayERRORS10,608 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,938 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT950 material changesacross 853 domains · +496 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination parity.domains · +20 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination pphosted.com · +4 vs yesterdayNOW2,719 curated domains not answering+504 vs yesterdayERRORS10,608 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,938 throttled or blocked our scanner429 rate-limit / 403 bot-block

capcom.co.jp

Observed 2026-07-15T13:58:24.254Z (2d ago). Every field below was attested with an Ed25519 signature at scan time.

Not responding
Runs onKDDI CORPORATION
Email byMicrosoft 365
Also usesGoogle Search Console
3 subdomains · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat capcom.co.jp actually stands on - every host below is a signed observation
capcom.co.jp
A / AAAA
106.185.74.121
KDDI CORPORATIONserves the site
NS
ns018-i9b7kctdchkfa5md.i.d-53.netns018-i9b7kctdchkfa5md.i.d-53.infons018-i9b7kctdchkfa5md.i.d-53.jp
d-53.net + d-53.info + moreanswers its DNS
MX
capcom-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

timeout No response within the timeout Connection timed out - no response within 3s
HTTP status0
Servernot observed
TLS protocolnot observed
TLS issuernot observed
Behind Cloudflareno
Response time6200 ms
DNS resolutionNOERROR

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 106.185.74.121

MX 1

  • 0capcom-com.mail.protection.outlook.com

TXT 10

  • v=spf1 include:h2hag6ft75.powerspf.com ~all
  • aeyescan-activation=8fa6a2ae575d3918
  • MS=ms56239072
  • google-site-verification=AU2RumgmgBHJ9xjLWWGzNytriF7quA5rixfcmU0vemw
  • 1bbclegdp9iruta0bued9voh2v
  • google-site-verification=IMmwjW7sALYzmSUypz1VCIdKjUnAm_Wr8xqpt4mLWtA
  • google-site-verification=e3flEd-1C4vORtJ0plGLx0QxgvggijHPIFoUO0m7Lrc
  • google-site-verification=rufxVzMwuOUEk91TBPbe1fbNOS1dVWnnO_XpYLen87g
  • v=DMARC1; p=none; rua=mailto:3rjefa3hfs@rua.powerdmarc.com; ruf=mailto:3rjefa3hfs@ruf.powerdmarc.com; fo=1;
  • v=DNSSEC1; (detected)

NS 3

  • ns018-i9b7kctdchkfa5md.i.d-53.net
  • ns018-i9b7kctdchkfa5md.i.d-53.info
  • ns018-i9b7kctdchkfa5md.i.d-53.jp

SOA 1

  • ns000.d-53.net dns-managers.iij.ad.jp

TLS Certificates (0)

None.

Subdomains (3)

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for capcom.co.jp. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for capcom.co.jp <a href="https://domaindrift.io/t/capcom.co.jp"> <img src="https://domaindrift.io/badge/capcom.co.jp.svg" width="300" height="64" alt="DomainDrift signed observations for capcom.co.jp"> </a>

Ed25519 Receipt

Receipt ID
b7ce2153-9932-4e4a-bb15-c80fa5ef252f
Output Hash
d63cf100dc16a629cc7d4cfe16f25f6d35c543ed23f8d51031ff038b7a822a2c
Signature
ed25519:52476d6ef5f10e8aff87662bb1495ce7311a1198d9833a6a4281b708bdb438a9c36ed55ec02674eb37fcd7b5dcd7c2930108d1614886029216fcd3b255795600
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser