lint.ai

Observed Aug 11, 2026, 06:06 UTC (14h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-11 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 lint.ai actually stands on - every host below is a signed observation
lint.ai
A / AAAA
18.217.231.63
unattributedserves the site
NS
ns-104.awsdns-13.comns-1436.awsdns-51.orgns-1832.awsdns-37.co.ukns-877.awsdns-45.net
awsdns-13.com + awsdns-51.org + moreanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comgyydvtl7pwd333hd545jg3bnicdsuea7fwhqnp2hkcmu6xx7hldq.mx-verification.google.com+2 more
Google Workspacereceives its email
TLS
golang.style
Let's Encryptissued its certificate

DNS Records

A 1

  • 18.217.231.63

MX 6

  • 0aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 15gyydvtl7pwd333hd545jg3bnicdsuea7fwhqnp2hkcmu6xx7hldq.mx-verification.google.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 1

  • v=spf1 include:_spf.google.com ~all

NS 4

  • ns-104.awsdns-13.com
  • ns-1436.awsdns-51.org
  • ns-1832.awsdns-37.co.uk
  • ns-877.awsdns-45.net

SOA 1

  • ns-877.awsdns-45.net awsdns-hostmaster.amazon.com

CAA 1

  • issue "letsencrypt.org"

MCP_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

BIMI_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

TLS Certificates (3)

Common NameIssuerExpires
golang.style C=US, O=Let's Encrypt, CN=YR1 Tue, 29 Sep 2026 12:48:24 +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 (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_e79e8add7c308d8a
Output Hash
0708c42ceeca9b4922284c9185ca6b2abb3d364b3277ce5eea33f1e8f27f9824
Signature
ed25519:ece0e9a1fb44f28a4ea8d58b383833cf361a224af24b9f990b3feae0c9ad5c6d4035eb9e613d29969371553e9472d1ade6d222746d69e31f56c8151acfb13003
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT7,345 material changesacross 4,412 domains · 24h to ~85m ago · -41,000 vs yesterdayDNS DRIFT83 domains changed DNS providertop destination koaladns.com · +1 vs yesterdayNOW523 curated domains not reachable-42 vs yesterdaySITE ERRORS35,971 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,667 sites429 rate-limit / 403 bot-block, a posture signal