md02.com
Observed Aug 12, 2026, 05:03 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.
md02.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting md02.com 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 md02.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Let's Encrypt
Google Search Console
YahooDomainDrift 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 2
144.217.32.44144.217.32.42
MX 1
10mail.md02.com
TXT 4
v=spf1 ip4:70.38.100.0/24 ip4:209.172.40.80/28 ip4:209.172.40.192/26 -allgoogle-site-verification=kl_lF2BORQR8ZnmehZ1MJSukIUcplyftwDuE4-tfb-gyahoo-verification-key=XCO5HGgAjvmMRDLlhjtLWc3EmRK+58nr1U9rY3DLLDk=google-site-verification=42ZmuJ_zdVTltTPlcOrkQr44mNh8hT_NWLXu_-ncih4
NS 5
nsm4.tckops.netnsm3.tckops.netnsm2.tckops.netnsm1.tckops.netnsm0.tckops.net
SOA 1
ns10.digicertdns.com dns.digicertdns.com
CAA 2
issue "letsencrypt.org"issue "digicert.com"
MCP_RECORDS 4
v=spf1 ip4:70.38.100.0/24 ip4:209.172.40.80/28 ip4:209.172.40.192/26 -allyahoo-verification-key=XCO5HGgAjvmMRDLlhjtLWc3EmRK+58nr1U9rY3DLLDk=google-site-verification=42ZmuJ_zdVTltTPlcOrkQr44mNh8hT_NWLXu_-ncih4google-site-verification=kl_lF2BORQR8ZnmehZ1MJSukIUcplyftwDuE4-tfb-g
DMARC_RECORDS 1
v=DMARC1; p=none; rua=mailto:vmwy5gsn@ag.us.dmarcian.com; ruf=mailto:vmwy5gsn@fr.us.dmarcian.com;
BIMI_RECORDS 4
google-site-verification=kl_lF2BORQR8ZnmehZ1MJSukIUcplyftwDuE4-tfb-gv=spf1 ip4:70.38.100.0/24 ip4:209.172.40.80/28 ip4:209.172.40.192/26 -allyahoo-verification-key=XCO5HGgAjvmMRDLlhjtLWc3EmRK+58nr1U9rY3DLLDk=google-site-verification=42ZmuJ_zdVTltTPlcOrkQr44mNh8hT_NWLXu_-ncih4
MTA_STS_RECORDS 4
yahoo-verification-key=XCO5HGgAjvmMRDLlhjtLWc3EmRK+58nr1U9rY3DLLDk=v=spf1 ip4:70.38.100.0/24 ip4:209.172.40.80/28 ip4:209.172.40.192/26 -allgoogle-site-verification=kl_lF2BORQR8ZnmehZ1MJSukIUcplyftwDuE4-tfb-ggoogle-site-verification=42ZmuJ_zdVTltTPlcOrkQr44mNh8hT_NWLXu_-ncih4
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
v3.md02.com |
C=US, O=Let's Encrypt, CN=YE1 | Mon, 09 Nov 2026 00:15:58 +0000 |
YE1 |
C=US, O=ISRG, CN=Root YE | Sat, 02 Sep 2028 23:59:59 +0000 |
Root YE |
C=US, O=Internet Security Research Group, CN=ISRG Root X2 | Thu, 02 Sep 2032 23:59:59 +0000 |
ISRG Root X2 |
C=US, O=Internet Security Research Group, CN=ISRG Root X1 | Thu, 02 Sep 2032 23:59:59 +0000 |
Subdomains (2)
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_b4269b36fa97edde- Output Hash
d7c045d9af4022338147df38f65c2a184cc05d8ba78d7863d6c89d7615603fd6- Signature
ed25519:0a0541b72ad5840b62450101782a2b7152d9e0827fbb4fd9854aa74228c68df3eb80c061e6a01e32a1c978fd632d9078d745d6421417dd26b1127757a422a00e- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast