CONTINUOUS INTERNET TELEMETRY24H DRIFT47,514 material changesacross 42,637 domains · 24h to ~2h ago · +13,108 vs yesterdayROTATION52 domains moved DNS from koaladns.com to magpiedns.com, 52 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,200 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,867 sites429 rate-limit / 403 bot-block, a posture signal

lbf.dk

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

This reading of lbf.dk was taken 7d ago

lbf.dk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lbf.dk 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 lbf.dk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byMicrosoft 365
Secured byLet's Encrypt
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 16:23 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 lbf.dk actually stands on - every host below is a signed observation
lbf.dk
A / AAAA
178.72.19.74
unattributedserves the site
NS
ns1-04.azure-dns.comns2-04.azure-dns.netns3-04.azure-dns.orgns4-04.azure-dns.info
azure-dns.com + azure-dns.net + moreanswers its DNS
MX
lbf-dk.mail.protection.outlook.com
Microsoft 365receives its email
TLS
lbf.dk
Let's Encryptissued its certificate

DNS Records

A 1

  • 178.72.19.74

MX 1

  • 10lbf-dk.mail.protection.outlook.com

TXT 1

  • v=spf1 include:_spf49800.spfprotect.com -all

NS 4

  • ns1-04.azure-dns.com
  • ns2-04.azure-dns.net
  • ns3-04.azure-dns.org
  • ns4-04.azure-dns.info

SOA 1

  • ns1-04.azure-dns.com azuredns-hostmaster.microsoft.com

MCP_RECORDS 1

  • v=spf1 redirect=lbf.dk

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100; fo=1; ri=3600; rua=mailto:6368f70b32b4a@dmarc.centerasecurity.com; ruf=mailto:med@bsf.dk;

BIMI_RECORDS 1

  • v=spf1 redirect=lbf.dk

MTA_STS_RECORDS 1

  • v=spf1 redirect=lbf.dk

TLS Certificates (3)

Common NameIssuerExpires
lbf.dk C=US, O=Let's Encrypt, CN=YR1 Sun, 25 Oct 2026 05:23:49 +0000
YR1 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.

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_0e5634afd4854812
Output Hash
71b4112a649d2b63032d9f6b0d92af3e12d32e8ad9efc309f39104e21301f9ec
Signature
ed25519:3c77b0d405e8a7e193494fcfc80079807ab9ebc88d94e77d23e4fb8891001a9fc36b3d7a43680536fb3fc18549707978d57684bc3085ae3b8963e4be22215e08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser