meetingplanner.pl

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

This reading of meetingplanner.pl was taken 2d ago

meetingplanner.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting meetingplanner.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 meetingplanner.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
2 subdomains · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 06:06 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 meetingplanner.pl actually stands on - every host below is a signed observation
meetingplanner.pl
A / AAAA
94.23.93.78
unattributedserves the site
NS
dns2.home.pldns3.home.pldns.home.pl
home.planswers its DNS
MX
serwer2501035.home.plserver859139.nazwa.pl
home.pl + nazwa.plreceives its email
TLS
meetingplanner.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 94.23.93.78

MX 2

  • 10serwer2501035.home.pl
  • 20server859139.nazwa.pl

TXT 1

  • v=spf1 a mx include:_spf.getresponse.com include:_spf.emaillabs.net.pl ~all

NS 3

  • dns2.home.pl
  • dns3.home.pl
  • dns.home.pl

SOA 1

  • dns.home.pl admin.home.pl

SRV 2

  • meetingplanner.pl:993 p10
  • meetingplanner.pl:587 p10

MCP_RECORDS 1

  • v=spf1 a mx include:_spf.getresponse.com include:_spf.emaillabs.net.pl ~all

DMARC_RECORDS 2

  • v=DMARC1; p=none;
  • v=DMARC1; p=none

BIMI_RECORDS 1

  • v=spf1 a mx include:_spf.getresponse.com include:_spf.emaillabs.net.pl ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx include:_spf.getresponse.com include:_spf.emaillabs.net.pl ~all

TLS Certificates (3)

Common NameIssuerExpires
meetingplanner.pl C=US, O=Let's Encrypt, CN=YR2 Fri, 02 Oct 2026 00:26:02 +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 (2)

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_b477da0c93082748
Output Hash
cff94b29c71ad601a069f861cf68f7282e313f1d066a227aa0e4bd29bb6f344e
Signature
ed25519:db11baaca5fd252703100d10d3e4d943e8cd01e5cd5a1f3f9859eca8277cd34b09b0195652dd6ad1cb5e90374b615e06cbbaeddefdfaffc60c46dd50c99b7209
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT46,461 material changesacross 44,568 domains · 24h to ~80m ago · +2,379 vs yesterdayROTATION64 domains moved DNS from koaladns.com to magpiedns.com, 61 moved backa rotation loop, not a migration · 24hNOW491 curated domains not reachablelast probe, steadySITE ERRORS36,518 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,184 sites429 rate-limit / 403 bot-block, a posture signal