jlamothe.net

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

This reading of jlamothe.net was taken 11d ago

jlamothe.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jlamothe.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 jlamothe.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
IPv6 · 1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 06:54 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 jlamothe.net actually stands on - every host below is a signed observation
jlamothe.net
A / AAAA
65.109.7.532a01:4f9:c010:ce96::1
2a01serves the site
NS
dns1.registrar-servers.comdns2.registrar-servers.com
registrar-servers.comanswers its DNS
MX
eforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.com+1 more
registrar-servers.comreceives its email
TLS
jlamothe.net
Let's Encryptissued its certificate

DNS Records

A 1

  • 65.109.7.53

AAAA 1

  • 2a01:4f9:c010:ce96::1

MX 5

  • 10eforward1.registrar-servers.com
  • 10eforward2.registrar-servers.com
  • 10eforward3.registrar-servers.com
  • 15eforward4.registrar-servers.com
  • 20eforward5.registrar-servers.com

TXT 1

  • v=spf1 a:jlamothe.net include:posteo.de ~all

NS 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

SOA 1

  • dns1.registrar-servers.com hostmaster.registrar-servers.com

MCP_RECORDS 1

  • v=spf1 a:jlamothe.net include:posteo.de ~all

DMARC_RECORDS 1

  • v=spf1 a:jlamothe.net include:posteo.de ~all

BIMI_RECORDS 1

  • v=spf1 a:jlamothe.net include:posteo.de ~all

MTA_STS_RECORDS 1

  • v=spf1 a:jlamothe.net include:posteo.de ~all

TLS Certificates (4)

Common NameIssuerExpires
jlamothe.net C=US, O=Let's Encrypt, CN=YE1 Wed, 07 Oct 2026 13:25:52 +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 (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_f7006da19d9c8e4d
Output Hash
8f0ecfa600b3891cbace75af5434e38166ab858856b2407f72737e5ceb9972fb
Signature
ed25519:a8d0cbd8a5569d0373c33b7069ed08088cc34f6a3bbd6d51f27654e029a6c97ff60e1f427dcdbe3d451dfac1097d5f91fb35a5c4c3326d61de7fb16044643a0d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,942 material changesacross 44,053 domains · 24h to ~2h ago · +1,860 vs yesterdayROTATION63 domains moved DNS from magpiedns.com to koaladns.com, 63 moved backa rotation loop, not a migration · 24hNOW491 curated domains not reachablelast probe, steadySITE ERRORS36,522 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,165 sites429 rate-limit / 403 bot-block, a posture signal