bexide.co.jp

Observed Aug 11, 2026, 02:46 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of bexide.co.jp was taken 3d ago

bexide.co.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bexide.co.jp under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch bexide.co.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onAutomattic
Email byGoogle Workspace
Secured byGoogle Trust Services
Also usesMicrosoft 365Atlassian
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 22:49 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat bexide.co.jp actually stands on - every host below is a signed observation
bexide.co.jp
A / AAAA
192.0.78.153192.0.78.251
Automatticserves the site
NS
ns3.wordpress.comns2.wordpress.comns1.wordpress.com
wordpress.comanswers its DNS
MX
aspmx3.googlemail.comaspmx5.googlemail.comalt1.aspmx.l.google.comalt2.aspmx.l.google.com+3 more
Google Workspacereceives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.153
  • 192.0.78.251

MX 7

  • 10aspmx3.googlemail.com
  • 10aspmx5.googlemail.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com
  • 10aspmx2.googlemail.com
  • 1aspmx.l.google.com
  • 10aspmx4.googlemail.com

TXT 4

  • 76d5c10b4b6c373f986eeb47874d6bd4cf851467900faebaa59d3ffc8f929761
  • v=spf1 include:_spf.wpcloud.com include:_spf.google.com ~all
  • atlassian-domain-verification=X2/J1su2QdOLk1G79BGatYuPSAcyGVzEesr3/YrPxLo0akq6sRjHifWVnVlUjZcU
  • MS=ms47919652

NS 3

  • ns3.wordpress.com
  • ns2.wordpress.com
  • ns1.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 4

  • 76d5c10b4b6c373f986eeb47874d6bd4cf851467900faebaa59d3ffc8f929761
  • v=spf1 include:_spf.wpcloud.com include:_spf.google.com ~all
  • atlassian-domain-verification=X2/J1su2QdOLk1G79BGatYuPSAcyGVzEesr3/YrPxLo0akq6sRjHifWVnVlUjZcU
  • MS=ms47919652

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 4

  • 76d5c10b4b6c373f986eeb47874d6bd4cf851467900faebaa59d3ffc8f929761
  • v=spf1 include:_spf.wpcloud.com include:_spf.google.com ~all
  • atlassian-domain-verification=X2/J1su2QdOLk1G79BGatYuPSAcyGVzEesr3/YrPxLo0akq6sRjHifWVnVlUjZcU
  • MS=ms47919652

MTA_STS_RECORDS 4

  • 76d5c10b4b6c373f986eeb47874d6bd4cf851467900faebaa59d3ffc8f929761
  • v=spf1 include:_spf.wpcloud.com include:_spf.google.com ~all
  • atlassian-domain-verification=X2/J1su2QdOLk1G79BGatYuPSAcyGVzEesr3/YrPxLo0akq6sRjHifWVnVlUjZcU
  • MS=ms47919652

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Wed, 21 Oct 2026 19:14:21 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (1)

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_0c467908d088661d
Output Hash
2c3f4ed9ee4e70419d6bd99e67d007df08ffb627bcbff94d02dcb0c0c8a40579
Signature
ed25519:af8bfa4f82ea0b1e699707d23225ab15c524ddffbd773de8ffd386f78656938f833558b5c6910795f25ea179fb0f61d6efab58fd2c188beba6a87f2431ccf80e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,493 material changesacross 45,291 domains · last 24h · +3,411 vs yesterdayROTATION60 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,336 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,530 sites429 rate-limit / 403 bot-block, a posture signal