black-up.kr
Observed Aug 10, 2026, 20:39 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
black-up.kr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting black-up.kr 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 black-up.kr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Let's Encrypt
Google Search ConsoleDomainDrift 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 4
183.111.139.230183.111.139.227183.111.139.231183.111.139.233
MX 3
10ecwebmail-011.cafe24.com11mx1.daouoffice.com12mx2.daouoffice.com
TXT 2
v=spf1 ip4:183.111.138.182 ip4:v=spf1 ip4:183.111.138.182 ~all ~allgoogle-site-verification=tdmanbCCfcn5f0MSAmA8m2j3xnxhkVi6OTqgp30ek9g
NS 4
ns.cafe24.comns2.cafe24.comns0.cafe24.comns1.cafe24.com
SOA 1
black-up.kr postmaster.black-up.kr
MCP_RECORDS 2
v=spf1 ip4:183.111.138.182 ip4:v=spf1 ip4:183.111.138.182 ~all ~allgoogle-site-verification=tdmanbCCfcn5f0MSAmA8m2j3xnxhkVi6OTqgp30ek9g
DMARC_RECORDS 2
google-site-verification=tdmanbCCfcn5f0MSAmA8m2j3xnxhkVi6OTqgp30ek9gv=spf1 ip4:183.111.138.182 ip4:v=spf1 ip4:183.111.138.182 ~all ~all
BIMI_RECORDS 2
google-site-verification=tdmanbCCfcn5f0MSAmA8m2j3xnxhkVi6OTqgp30ek9gv=spf1 ip4:183.111.138.182 ip4:v=spf1 ip4:183.111.138.182 ~all ~all
MTA_STS_RECORDS 2
google-site-verification=tdmanbCCfcn5f0MSAmA8m2j3xnxhkVi6OTqgp30ek9gv=spf1 ip4:183.111.138.182 ip4:v=spf1 ip4:183.111.138.182 ~all ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
black-up.kr |
C=US, O=Let's Encrypt, CN=YR2 | Sun, 01 Nov 2026 15:01:52 +0000 |
YR2 |
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 (4)
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_e9bdb513ebe42a6f- Output Hash
02e7effbecbfce9ad41dfd5182e69c7e0bc94a54e0e294bb2b066f5e97208a46- Signature
ed25519:d65c51919b48d0c7086fe8943739491b1098c4b1b5763047632baa3382ad140adbd485c016e9ee589ef13df676d989ae5ae75be269ac5274e32a2a2ed5fcfa06- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast