CONTINUOUS INTERNET TELEMETRY24H DRIFT71,617 material changesacross 67,026 domains · 24h to ~35m ago · +37,000 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW533 curated domains not reachablelast probe, steadySITE ERRORS33,847 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 126,417 sites429 rate-limit / 403 bot-block, a posture signal

provider.lk

Observed Jul 24, 2026, 19:39 UTC (12d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of provider.lk was taken 12d ago

provider.lk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting provider.lk 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 provider.lk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byGoogle Workspace
Secured byZeroSSL GmbH
Also usesGoogle Search Console
IPv6 · tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 12:38 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 provider.lk actually stands on - every host below is a signed observation
provider.lk
A / AAAA
185.206.180.113185.206.180.1752a0b:1640:1:1:1016:1:1:12a0b:1640:1:1:1:1:e51:8afc
Cloudflareserves the site
NS
ns4.provider.lkns2.provider.lkns3.provider.lkns1.provider.lk
provider.lkanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
provider.lk
ZeroSSL GmbHissued its certificate

DNS Records

A 2

  • 185.206.180.113
  • 185.206.180.175

AAAA 2

  • 2a0b:1640:1:1:1016:1:1:1
  • 2a0b:1640:1:1:1:1:e51:8afc

MX 5

  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 6

  • google-site-verification=kyNyrQPpmGjIzM5CoZREEd8plSByIKK-0m4P4Vr_CKc
  • v=spf1 include:_spf.google.com include:mailgun.org include:_s00002163.autospf.email ip4:51.38.35.71 ~all
  • v=spf1 include:_spf.google.com include:mailgun.org include:_s00002163.autospf.email ip4:51.38.35.71 ~all
  • v=spf1 include:_spf.google.com include:mailgun.org include:_s00002163.autospf.email ip4:51.38.35.71 ~all
  • v=spf1 include:_spf.google.com include:mailgun.org include:_s00002163.autospf.email ip4:51.38.35.71 ~all
  • v=spf1 include:_spf.google.com include:mailgun.org include:_s00002163.autospf.email ip4:51.38.35.71 ~all

NS 4

  • ns4.provider.lk
  • ns2.provider.lk
  • ns3.provider.lk
  • ns1.provider.lk

SOA 1

  • ns1.provider.lk info.provider.lk

TLS Certificates (3)

Common NameIssuerExpires
provider.lk C=AT, O=ZeroSSL GmbH, CN=ZeroSSL ECC DV SSL CA 2 Wed, 07 Oct 2026 23:59:59 +0000
ZeroSSL ECC DV SSL CA 2 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root E46 Sun, 23 Sep 2035 23:59:59 +0000
Sectigo Public Server Authentication Root E46 C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust ECC Certification Authority Mon, 18 Jan 2038 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_9d454c3f01e3589d
Output Hash
d6356cd491eb34f08d792ada4a50cf516ca356e0774af1dfc42fa54ba05aa100
Signature
ed25519:6206dc3077a5a46f5d20973723f5bab8cdb2c25e988ed1b54a8722b8432f5c1b74a0c751bf69389f00636815bc56b2024221647ba255eca924a181cb1f556e09
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser