jrcs.net

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

This reading of jrcs.net was taken 13d ago

jrcs.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jrcs.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 jrcs.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 11:18 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 jrcs.net actually stands on - every host below is a signed observation
jrcs.net
A / AAAA
82.68.70.16382.68.70.162
unattributedserves the site
NS
ns1.jrcs.netns2.jrcs.netns3.jrcs.net
jrcs.netanswers its DNS
MX
mx10.jrcs.net
jrcs.netreceives its email
TLS
*.jrcs.net
Let's Encryptissued its certificate

DNS Records

A 2

  • 82.68.70.163
  • 82.68.70.162

MX 1

  • 10mx10.jrcs.net

TXT 1

  • v=spf1 ip4:82.68.70.174 mx include:_spf.zen.co.uk include:megamailservers.eu -all

NS 3

  • ns1.jrcs.net
  • ns2.jrcs.net
  • ns3.jrcs.net

SOA 1

  • ns1.jrcs.net dns.jrcs.net

MCP_RECORDS 1

  • Nameshake/LHR/4

DMARC_RECORDS 1

  • Nameshake/LHR/4

BIMI_RECORDS 1

  • Nameshake/LHR/3

MTA_STS_RECORDS 1

  • Nameshake/LHR/4

TLS Certificates (4)

Common NameIssuerExpires
*.jrcs.net C=US, O=Let's Encrypt, CN=YE1 Thu, 24 Sep 2026 10:02:37 +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 (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_a435f904e78a3941
Output Hash
56800b993692ce8d7c69c2a7c439d17efde12ea5aa8dd0566be56fcf282bd7b7
Signature
ed25519:791c55075d1bf7b4b972d3f39b10cf37aee0db0ff91bea4485eba4cafddfdc161d203d6873a74e87214a02478df93bc77d623aa91390d7022b130e06e933db0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,228 material changesacross 42,540 domains · 24h to ~80m ago · +721 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW497 curated domains not reachablelast probe, steadySITE ERRORS36,281 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,270 sites429 rate-limit / 403 bot-block, a posture signal