merukore.jp
Observed Aug 16, 2026, 07:15 UTC (3h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
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.
DNS Records
A 1
103.13.152.202
MX 1
10merukore.jp
TXT 1
v=spf1 +ip4:103.13.154.0/23 +ip4:182.54.248.0/23 +ip4:103.13.152.0/23 ~all
NS 4
01.dnsv.jp02.dnsv.jp03.dnsv.jp04.dnsv.jp
SOA 1
01.dnsv.jp hostmaster.dnsv.jp
MCP_RECORDS 1
v=spf1 +ip4:103.13.154.0/23 +ip4:182.54.248.0/23 +ip4:103.13.152.0/23 ~all
DMARC_RECORDS 1
v=DMARC1; p=none; sp=none; rua=mailto:report@merukore.jp; ruf=mailto:report@merukore.jp
BIMI_RECORDS 1
v=spf1 +ip4:103.13.154.0/23 +ip4:182.54.248.0/23 +ip4:103.13.152.0/23 ~all
MTA_STS_RECORDS 1
v=spf1 +ip4:103.13.154.0/23 +ip4:182.54.248.0/23 +ip4:103.13.152.0/23 ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
merukore.jp |
C=US, O=Let's Encrypt, CN=YR1 | Sat, 03 Oct 2026 19:33:59 +0000 |
YR1 |
C=US, O=ISRG, CN=Root YR | Sat, 02 Sep 2028 23:59:59 +0000 |
Root YR |
C=US, O=Internet Security Research Group, CN=ISRG Root X1 | Thu, 02 Sep 2032 23:59:59 +0000 |
Subdomains (0)
None observed.
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 receiptEd25519 Receipt
- Receipt ID
rcpt_ab6df305e60b00ff- Output Hash
6848793098b89439892ab394c90e1568de8324fe6e14167b8cb79167a0f94281- Signature
ed25519:327d99b3768ebeb43c9783a73a562211e53a70646ef113b439dcfa1e1f41d350fa9d7695a0001688527bebbd714e319fbe6828cf972f71c858399b0a47ff4a05- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast