autogielda.pl

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

This reading of autogielda.pl was taken 6d ago

autogielda.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting autogielda.pl 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 autogielda.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Runs onOVH SAS
Secured byLet's Encrypt
Registered toZagórny
Registered withnazwa.pl sp. z o.o.
Also usesGoogle Search Console
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for autogielda.pl in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

INFRASTRUCTURE MAPwhat autogielda.pl actually stands on - every host below is a signed observation
autogielda.pl
A / AAAA
51.77.36.50
OVH SASserves the site
NS
james.ns.cloudflare.comnelly.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mx2.autogielda.pl
autogielda.plreceives its email
TLS
autogielda.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 51.77.36.50

MX 1

  • 0mx2.autogielda.pl

TXT 3

  • google-site-verification=TofjeUvnqQbpSTKgYhg2ebaOombF_XEHhAFc_3P9FXU
  • google-site-verification=pSkNUhWtkoRJ7s93MMmVMaJwVd1WbquH_Jxb_GBtGRg
  • v=spf1 a mx ptr ip4:51.77.36.49 ip4:94.23.170.229 ip4:5.196.241.93 ip4:91.198.209.49 ip4:91.198.209.2 ip4:91.198.209.3 ip4:91.198.209.61 ip4:91.198.209.15 ip4:193.70.54.95 -all

NS 2

  • james.ns.cloudflare.com
  • nelly.ns.cloudflare.com

SOA 1

  • james.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 3

  • google-site-verification=TofjeUvnqQbpSTKgYhg2ebaOombF_XEHhAFc_3P9FXU
  • google-site-verification=pSkNUhWtkoRJ7s93MMmVMaJwVd1WbquH_Jxb_GBtGRg
  • v=spf1 a mx ptr ip4:51.77.36.49 ip4:94.23.170.229 ip4:5.196.241.93 ip4:91.198.209.49 ip4:91.198.209.2 ip4:91.198.209.3 ip4:91.198.209.61 ip4:91.198.209.15 ip4:193.70.54.95 -all

DMARC_RECORDS 3

  • google-site-verification=TofjeUvnqQbpSTKgYhg2ebaOombF_XEHhAFc_3P9FXU
  • google-site-verification=pSkNUhWtkoRJ7s93MMmVMaJwVd1WbquH_Jxb_GBtGRg
  • v=spf1 a mx ptr ip4:51.77.36.49 ip4:94.23.170.229 ip4:5.196.241.93 ip4:91.198.209.49 ip4:91.198.209.2 ip4:91.198.209.3 ip4:91.198.209.61 ip4:91.198.209.15 ip4:193.70.54.95 -all

BIMI_RECORDS 3

  • google-site-verification=TofjeUvnqQbpSTKgYhg2ebaOombF_XEHhAFc_3P9FXU
  • google-site-verification=pSkNUhWtkoRJ7s93MMmVMaJwVd1WbquH_Jxb_GBtGRg
  • v=spf1 a mx ptr ip4:51.77.36.49 ip4:94.23.170.229 ip4:5.196.241.93 ip4:91.198.209.49 ip4:91.198.209.2 ip4:91.198.209.3 ip4:91.198.209.61 ip4:91.198.209.15 ip4:193.70.54.95 -all

MTA_STS_RECORDS 3

  • google-site-verification=TofjeUvnqQbpSTKgYhg2ebaOombF_XEHhAFc_3P9FXU
  • google-site-verification=pSkNUhWtkoRJ7s93MMmVMaJwVd1WbquH_Jxb_GBtGRg
  • v=spf1 a mx ptr ip4:51.77.36.49 ip4:94.23.170.229 ip4:5.196.241.93 ip4:91.198.209.49 ip4:91.198.209.2 ip4:91.198.209.3 ip4:91.198.209.61 ip4:91.198.209.15 ip4:193.70.54.95 -all

TLS Certificates (3)

Common NameIssuerExpires
autogielda.pl C=US, O=Let's Encrypt, CN=YR2 Thu, 08 Oct 2026 20:41:28 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-16 20:51 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way.

How the check works, and what it shows

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_27a80bed73094314
Output Hash
69dc72cc730a421fc024c4d1a0f7b800fe3b062af01493c8ca2b26ed7aaee2bf
Signature
ed25519:2b8581b6203cefe44c81f2d8581a500b0fd76f2362e26e58468b7ddc49e3a2dd590e4d71bbda6dc9b98603d0257a49b71f94b08eda2daaa60ce9b7538dae800d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT37,477 material changesacross 35,826 domains · 24h to ~3h ago · -1,763 vs yesterdayROTATION59 domains moved DNS from magpiedns.com to koaladns.com, 58 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW591 curated domains not reachablelast probe, steadySITE ERRORS35,522 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,252 sites429 rate-limit / 403 bot-block, a posture signal