bogatynia.pl
Observed Aug 11, 2026, 03:00 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.
bogatynia.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bogatynia.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 bogatynia.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Microsoft 365Steady. No change on record for bogatynia.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.
DNS Records
A 1
89.161.251.180
MX 1
10bogatynia.pl
TXT 2
MS=ms42707547v=spf1 ip4:89.161.175.6 a mx ~all
NS 3
dns.home.pldns2.home.pldns3.home.pl
SOA 1
dns.home.pl admin.home.pl
MCP_RECORDS 2
MS=ms42707547v=spf1 ip4:89.161.175.6 a mx ~all
DMARC_RECORDS 1
v=DMARC1; p=reject; pct=100; rua=mailto:sec@bogatynia.pl; rf=afrf
BIMI_RECORDS 2
MS=ms42707547v=spf1 ip4:89.161.175.6 a mx ~all
MTA_STS_RECORDS 2
MS=ms42707547v=spf1 ip4:89.161.175.6 a mx ~all
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
*.bogatynia.pl |
C=PL, O=home.pl S.A., CN=home pl DV TLS G2 R35 CA | Fri, 18 Dec 2026 17:22:32 +0000 |
home pl DV TLS G2 R35 CA |
C=PL, O=Asseco Data Systems S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Root CA | Wed, 16 May 2035 07:45:35 +0000 |
Certum Trusted Root CA |
C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA | Tue, 19 Sep 2028 10:00:00 +0000 |
Certum Trusted Network CA |
C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA | Mon, 31 Dec 2029 12:07:37 +0000 |
Subdomains (0)
None observed.
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
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 receiptEd25519 Receipt
- Receipt ID
rcpt_904c027594f48267- Output Hash
292b09718d807d53349bf8ef2909078ef80676088e429d1fe60082967c769f50- Signature
ed25519:c3e3210ca4aee93287b185b6b415753341a804f4f24fe5ed8ea3c1ae1e68232b926590fffd00b69a266a5a897f5a9f39f77d59cd72104ca9e468b4637228e003- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast