bizloop.jp

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

This reading of bizloop.jp was taken 3d ago

bizloop.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bizloop.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 bizloop.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onAmazon
Secured byAmazon
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 01:22 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 bizloop.jp actually stands on - every host below is a signed observation
bizloop.jp
A / AAAA
52.196.3.4952.197.70.176
Amazonserves the site
NS
ns-1133.awsdns-13.orgns-1780.awsdns-30.co.ukns-456.awsdns-57.comns-877.awsdns-45.net
awsdns-13.org + awsdns-30.co.uk + moreanswers its DNS
MX
www1.bizloop.jp
bizloop.jpreceives its email
TLS
*.bizloop.jp
Amazonissued its certificate

DNS Records

A 2

  • 52.196.3.49
  • 52.197.70.176

MX 1

  • 10www1.bizloop.jp

TXT 3

  • google-site-verification=Mzb_aWx5S0VH99slpC9cLtPN_-YO1etQCToKE0MdIQI
  • google-site-verification=O7dEdqWCWfS-QQMjZVmu6_vKcPruiKQ3Ka_1As1zNFw
  • v=spf1 +ip4:52.69.17.13 +ip4:18.179.230.165 +a:cad0.spf.cloud-mail.jp ~all

NS 4

  • ns-1133.awsdns-13.org
  • ns-1780.awsdns-30.co.uk
  • ns-456.awsdns-57.com
  • ns-877.awsdns-45.net

SOA 1

  • ns-877.awsdns-45.net awsdns-hostmaster.amazon.com

MCP_RECORDS 3

  • google-site-verification=Mzb_aWx5S0VH99slpC9cLtPN_-YO1etQCToKE0MdIQI
  • google-site-verification=O7dEdqWCWfS-QQMjZVmu6_vKcPruiKQ3Ka_1As1zNFw
  • v=spf1 +ip4:52.69.17.13 +ip4:18.179.230.165 +a:cad0.spf.cloud-mail.jp ~all

DMARC_RECORDS 3

  • google-site-verification=Mzb_aWx5S0VH99slpC9cLtPN_-YO1etQCToKE0MdIQI
  • google-site-verification=O7dEdqWCWfS-QQMjZVmu6_vKcPruiKQ3Ka_1As1zNFw
  • v=spf1 +ip4:52.69.17.13 +ip4:18.179.230.165 +a:cad0.spf.cloud-mail.jp ~all

BIMI_RECORDS 3

  • google-site-verification=Mzb_aWx5S0VH99slpC9cLtPN_-YO1etQCToKE0MdIQI
  • google-site-verification=O7dEdqWCWfS-QQMjZVmu6_vKcPruiKQ3Ka_1As1zNFw
  • v=spf1 +ip4:52.69.17.13 +ip4:18.179.230.165 +a:cad0.spf.cloud-mail.jp ~all

MTA_STS_RECORDS 3

  • google-site-verification=Mzb_aWx5S0VH99slpC9cLtPN_-YO1etQCToKE0MdIQI
  • google-site-verification=O7dEdqWCWfS-QQMjZVmu6_vKcPruiKQ3Ka_1As1zNFw
  • v=spf1 +ip4:52.69.17.13 +ip4:18.179.230.165 +a:cad0.spf.cloud-mail.jp ~all

TLS Certificates (3)

Common NameIssuerExpires
*.bizloop.jp C=US, O=Amazon, CN=Amazon RSA 2048 M04 Wed, 17 Mar 2027 23:59:59 +0000
Amazon RSA 2048 M04 C=US, O=Amazon, CN=Amazon Root CA 1 Fri, 23 Aug 2030 22:26:35 +0000
Amazon Root CA 1 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2 Thu, 31 Dec 2037 01:00:00 +0000

Subdomains (0)

None observed.

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_bfa5c97974e6b339
Output Hash
29272fa5df95fedad1a66ad52c6db44acb207fdf926fe91321ee4b598b2904b8
Signature
ed25519:3695592308d44d03b186a26d7ed3cdbbe6fd784960421128402655980ffa9f8fda4641c949bb7db57be613f92b95a8b20c35405320c862388f95a8630578ff08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,493 material changesacross 45,291 domains · 24h to ~50m ago · +3,411 vs yesterdayROTATION59 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,357 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,561 sites429 rate-limit / 403 bot-block, a posture signal