CONTINUOUS INTERNET TELEMETRY24H DRIFT29,105 material changesacross 28,144 domains · 24h to ~12h ago · -8,917 vs yesterdayROTATION59 domains moved DNS from kirklanddc.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW556 curated domains not reachable+25 vs yesterdaySITE ERRORS33,755 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,583 sites429 rate-limit / 403 bot-block, a posture signal

lipton.jp

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

This reading of lipton.jp was taken 5d ago

lipton.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lipton.jp 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 lipton.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byAmazon SES
Secured byLet's Encrypt
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 18:40 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 lipton.jp actually stands on - every host below is a signed observation
lipton.jp
A / AAAA
75.2.60.5
unattributedserves the site
NS
ns1-32.azure-dns.comns2-32.azure-dns.netns3-32.azure-dns.orgns4-32.azure-dns.info
azure-dns.com + azure-dns.net + moreanswers its DNS
TLS
www.lipton.jp
Let's Encryptissued its certificate

DNS Records

A 1

  • 75.2.60.5

TXT 1

  • v=spf1 mx a +ip4:13.113.56.65 include:amazonses.com -all

NS 4

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

SOA 1

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

MCP_RECORDS 1

  • v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:postmaster@dms.unileverservices.com

BIMI_RECORDS 1

  • v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all

MTA_STS_RECORDS 1

  • v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all

TLS Certificates (4)

Common NameIssuerExpires
www.lipton.jp C=US, O=Let's Encrypt, CN=YE2 Sat, 10 Oct 2026 18:23:50 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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_5694c465582645fd
Output Hash
48ab932e945aeab0349a71e51088e987b371fd694373db4170ed56038dd9bb77
Signature
ed25519:d4813bc8ecda05043f254431bd53d190f6a284d5ecafecb3a0d57a13cf649fa791941b5329210fa11397377857a4453f8e0f36f05ddca32a2c65f9049f4c2605
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser