reneritchie.net

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

This reading of reneritchie.net was taken 3d ago

reneritchie.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting reneritchie.net 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 reneritchie.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoogle Trust Services
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 02:21 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 reneritchie.net actually stands on - every host below is a signed observation
reneritchie.net
A / AAAA
192.0.78.244192.0.78.153
unattributedserves the site
NS
ns2.wordpress.comns1.wordpress.comns3.wordpress.com
wordpress.comanswers its DNS
MX
mx.hover.com.cust.hostedemail.com
hostedemail.comreceives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.244
  • 192.0.78.153

MX 1

  • 10mx.hover.com.cust.hostedemail.com

TXT 1

  • v=spf1 include:_spf.wpcloud.com ~all

NS 3

  • ns2.wordpress.com
  • ns1.wordpress.com
  • ns3.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Sun, 04 Oct 2026 07:27:39 +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 (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_d77e5db2422c5c96
Output Hash
1cf24e43bf07f4f3952fd5c18467f5e4db2c0565072ba9a985349f3baa855ab3
Signature
ed25519:faeed858ddc4bd1238f33d4cbb6211befbd7bc4fea99e3d78f4e8e3682120838012481e1ef3175deba24cc58951e4e76e9c442de7f5938833cdfdd082fb0f500
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,295 material changesacross 45,163 domains · last 24h · +3,213 vs yesterdayROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 51 moved backa rotation loop, not a migration · 24hNOW490 curated domains not reachablelast probe, steadySITE ERRORS36,446 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,510 sites429 rate-limit / 403 bot-block, a posture signal