jralonso.es

Observed Aug 10, 2026, 05:27 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of jralonso.es was taken 5d ago

jralonso.es is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jralonso.es 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 jralonso.es 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 11:25 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 jralonso.es actually stands on - every host below is a signed observation
jralonso.es
A / AAAA
192.0.78.159192.0.78.254
unattributedserves the site
NS
ns2.wordpress.comns3.wordpress.comns1.wordpress.com
wordpress.comanswers its DNS
MX
smtp-01.piensasolutions.com
piensasolutions.comreceives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.159
  • 192.0.78.254

MX 1

  • 10smtp-01.piensasolutions.com

TXT 1

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

NS 3

  • ns2.wordpress.com
  • ns3.wordpress.com
  • ns1.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 Tue, 06 Oct 2026 09:52:58 +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_4f765e2821d85ee2
Output Hash
f204fbda8cdeebe34667debebb6b10065d78b1bc8147c7687c2f10e8048f59ee
Signature
ed25519:8dbce63c67d4bc5c24909b17888042ee6ef5c8cb58ba2fc7c07eba85c14f8ce098182ca33740ef37fbd5287548dc31dff8609ca1ebaf8740f8ffaac85ee65400
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,889 material changesacross 44,128 domains · 24h to ~70m ago · +2,382 vs yesterdayROTATION60 domains moved DNS from magpiedns.com to koaladns.com, 59 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,298 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,222 sites429 rate-limit / 403 bot-block, a posture signal