joycearthur.com

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

This reading of joycearthur.com was taken 3d ago

joycearthur.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting joycearthur.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 joycearthur.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoogle Trust Services
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 04:55 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 joycearthur.com actually stands on - every host below is a signed observation
joycearthur.com
A / AAAA
192.0.78.24192.0.78.25
unattributedserves the site
NS
ns3.wordpress.comns1.wordpress.comns2.wordpress.com
wordpress.comanswers its DNS
MX
web218.dnchosting.com
dnchosting.comreceives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.24
  • 192.0.78.25

MX 1

  • 10web218.dnchosting.com

TXT 1

  • v=spf1 +mx +a +ip4:192.64.150.218 ~all

NS 3

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

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • v=spf1 +mx +a +ip4:192.64.150.218 ~all

DMARC_RECORDS 1

  • v=spf1 +mx +a +ip4:192.64.150.218 ~all

BIMI_RECORDS 1

  • v=spf1 +mx +a +ip4:192.64.150.218 ~all

MTA_STS_RECORDS 1

  • v=spf1 +mx +a +ip4:192.64.150.218 ~all

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Sat, 10 Oct 2026 20:38:56 +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)

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_c329795ec40ece9c
Output Hash
41f6db00655a508f01ec0ae9c768c2a889f655151006c62ffc45bdec30260738
Signature
ed25519:fb66d1d1beddfe20f04a0963b88144a18cfc200c4ed7dc44db600a07bcdfd586b0b0661937299c96ff6c78ed475504f206a1968b588360eb4efa44a174379302
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,927 material changesacross 43,159 domains · 24h to ~60m ago · +1,420 vs yesterdayROTATION61 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,383 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,323 sites429 rate-limit / 403 bot-block, a posture signal