medic.org
Observed Aug 12, 2026, 05:02 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.
medic.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting medic.org 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 medic.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google Workspace
Google Trust Services
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 2
192.0.78.178192.0.78.202
MX 5
1aspmx.l.google.com10alt4.aspmx.l.google.com5alt1.aspmx.l.google.com10alt3.aspmx.l.google.com5alt2.aspmx.l.google.com
TXT 2
v=spf1 include:_spf.google.com include:_spf.wpcloud.com ~allgoogle-site-verification=OdBv8OcbiVml4LuYBwcebOfB38S1eZxeCoaBkgOABxs
NS 3
ns1.wordpress.comns2.wordpress.comns3.wordpress.com
SOA 1
ns1.wordpress.com hostmaster.wordpress.com
MCP_RECORDS 2
v=spf1 include:_spf.google.com include:_spf.wpcloud.com ~allgoogle-site-verification=OdBv8OcbiVml4LuYBwcebOfB38S1eZxeCoaBkgOABxs
DMARC_RECORDS 1
v=DMARC1; p=none;
BIMI_RECORDS 2
v=spf1 include:_spf.google.com include:_spf.wpcloud.com ~allgoogle-site-verification=OdBv8OcbiVml4LuYBwcebOfB38S1eZxeCoaBkgOABxs
MTA_STS_RECORDS 2
v=spf1 include:_spf.google.com include:_spf.wpcloud.com ~allgoogle-site-verification=OdBv8OcbiVml4LuYBwcebOfB38S1eZxeCoaBkgOABxs
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
tls.automattic.com |
C=US, O=Google Trust Services, CN=WR1 | Wed, 30 Sep 2026 20:46:25 +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)
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_72f31e24e0b805e9- Output Hash
305f80eed2faff60ef2d3529c2be8a00669ab1e91ea5413a82899fc79be0faf7- Signature
ed25519:412d295f3394865840fc57de34fe3bf1af4019e1bfaa25155df461f0b5dd012ebc6c0972fd6ae1771d443009bee93856c0cd9e28ef5bf80a33ff53aef061030e- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast