CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · last 24hROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,101 sites429 rate-limit / 403 bot-block, a posture signal

lipsurf.com

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

This reading of lipsurf.com was taken 6d ago

lipsurf.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lipsurf.com 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 lipsurf.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byAmazon
Also usesGoogle Search Console
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 17:19 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 lipsurf.com actually stands on - every host below is a signed observation
lipsurf.com
A / AAAA
3.162.103.523.162.103.803.162.103.1183.162.103.62
unattributedserves the site
NS
ns-110.awsdns-13.comns-1197.awsdns-21.orgns-1711.awsdns-21.co.ukns-959.awsdns-55.net
awsdns-13.com + awsdns-21.org + moreanswers its DNS
MX
in1-smtp.messagingengine.comin2-smtp.messagingengine.com
messagingengine.comreceives its email
TLS
*.lipsurf.com
Amazonissued its certificate

DNS Records

A 4

  • 3.162.103.52
  • 3.162.103.80
  • 3.162.103.118
  • 3.162.103.62

MX 2

  • 10in1-smtp.messagingengine.com
  • 20in2-smtp.messagingengine.com

TXT 5

  • MS=AE53756867E18A76BA0F7EA3BF88298417756E21
  • firebase=lipsurf-216216
  • google-site-verification=jlgVtzAqT7F29iGQntpRlZBM0efpxHstqKQOzRposJ0
  • google-site-verification=zAnXdIImttWR5gYR4vv4FHj7DxKMcMu3fLfhTtbpXFg
  • v=spf1 include:_spf.firebasemail.com include:spf.messagingengine.com ~all

NS 4

  • ns-110.awsdns-13.com
  • ns-1197.awsdns-21.org
  • ns-1711.awsdns-21.co.uk
  • ns-959.awsdns-55.net

SOA 1

  • ns-1197.awsdns-21.org awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • v=spf1 include:spf.messagingengine.com ?all

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • v=spf1 include:spf.messagingengine.com ?all

MTA_STS_RECORDS 1

  • v=spf1 include:spf.messagingengine.com ?all

TLS Certificates (3)

Common NameIssuerExpires
*.lipsurf.com C=US, O=Amazon, CN=Amazon RSA 2048 M04 Fri, 16 Oct 2026 23:59:59 +0000
Amazon RSA 2048 M04 C=US, O=Amazon, CN=Amazon Root CA 1 Fri, 23 Aug 2030 22:26:35 +0000
Amazon Root CA 1 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2 Thu, 31 Dec 2037 01:00:00 +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_756c04115be6d914
Output Hash
d60a2393b046effcf9f3df9191f3ddeeb926202037ab6c55b45601b2568ba89c
Signature
ed25519:6ebbf52861ac14e0539b7f3ed0cc86fbd80640a0e498a0c8df58cb98760690f30cdb484c91be1e587712ba4c0bf270c9cacb61ed5ff2e14fcb87d1448c375603
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser