CONTINUOUS INTERNET TELEMETRY24H DRIFT27,060 material changesacross 26,158 domains · 24h to ~14h ago · -10,962 vs yesterdayROTATION58 domains moved DNS from kirklanddc.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW562 curated domains not reachable+31 vs yesterdaySITE ERRORS33,728 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,775 sites429 rate-limit / 403 bot-block, a posture signal

lecturalia.com

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

This reading of lecturalia.com was taken 4d ago

lecturalia.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lecturalia.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 lecturalia.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured bySoluciones Corporativas IP SL
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 04:48 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 lecturalia.com actually stands on - every host below is a signed observation
lecturalia.com
A / AAAA
93.93.64.123
unattributedserves the site
NS
dns3.hispalisdns.comdns1.hispalisdns.comdns2.hispalisdns.com
hispalisdns.comanswers its DNS
MX
mail.lecturalia.com
lecturalia.comreceives its email
TLS
*.lecturalia.com
Soluciones Corporativas IP SLissued its certificate

DNS Records

A 1

  • 93.93.64.123

MX 1

  • 10mail.lecturalia.com

TXT 3

  • v=spf1 mx include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com a:mail.lecturalia.com ip4:195.78.228.0/22 ip4:77.81.116.0/22 ip4:91.192.108.0/22 ip4:93.93.64.0/21 ip4:5.145.168.0/21 ip6:2a00:1d70::/32 -all
  • ahrefs-site-verification_21564fe34ec8ccb9345948c303eb13c70f3efdce35742d680b2c0b8bbab630d0
  • google-site-verification=av-XD4NGUTUJgzQkPYLl6NzgiSHDHpzG8qVXN9D2Euw

NS 3

  • dns3.hispalisdns.com
  • dns1.hispalisdns.com
  • dns2.hispalisdns.com

SOA 1

  • dns1.hispalisdns.com admin.furanet.com

MCP_RECORDS 3

  • v=spf1 mx include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com a:mail.lecturalia.com ip4:195.78.228.0/22 ip4:77.81.116.0/22 ip4:91.192.108.0/22 ip4:93.93.64.0/21 ip4:5.145.168.0/21 ip6:2a00:1d70::/32 -all
  • ahrefs-site-verification_21564fe34ec8ccb9345948c303eb13c70f3efdce35742d680b2c0b8bbab630d0
  • google-site-verification=av-XD4NGUTUJgzQkPYLl6NzgiSHDHpzG8qVXN9D2Euw

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100; aspf=s; adkim=s

BIMI_RECORDS 3

  • v=spf1 mx include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com a:mail.lecturalia.com ip4:195.78.228.0/22 ip4:77.81.116.0/22 ip4:91.192.108.0/22 ip4:93.93.64.0/21 ip4:5.145.168.0/21 ip6:2a00:1d70::/32 -all
  • ahrefs-site-verification_21564fe34ec8ccb9345948c303eb13c70f3efdce35742d680b2c0b8bbab630d0
  • google-site-verification=av-XD4NGUTUJgzQkPYLl6NzgiSHDHpzG8qVXN9D2Euw

MTA_STS_RECORDS 3

  • v=spf1 mx include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com a:mail.lecturalia.com ip4:195.78.228.0/22 ip4:77.81.116.0/22 ip4:91.192.108.0/22 ip4:93.93.64.0/21 ip4:5.145.168.0/21 ip6:2a00:1d70::/32 -all
  • ahrefs-site-verification_21564fe34ec8ccb9345948c303eb13c70f3efdce35742d680b2c0b8bbab630d0
  • google-site-verification=av-XD4NGUTUJgzQkPYLl6NzgiSHDHpzG8qVXN9D2Euw

TLS Certificates (4)

Common NameIssuerExpires
*.lecturalia.com C=ES, O=Soluciones Corporativas IP SL, CN=Don Dominio RSA DV SSL CA 2 Thu, 08 Oct 2026 23:59:59 +0000
Don Dominio RSA DV SSL CA 2 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Sun, 13 May 2035 23:59:59 +0000
Sectigo Public Server Authentication Root R46 C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority Mon, 18 Jan 2038 23:59:59 +0000
USERTrust RSA Certification Authority C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA 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_c1d46f049912d8b8
Output Hash
637d22482ba7a0c761970137401e256dc2f5492753b60d059d34b4ed879011b5
Signature
ed25519:9749aa6bb42b4d2bdb319680842568a45a48fc715f77607a2e422875d62381577a136b6518ae9385c71c4bcf43207e6512b8667fbfc6db4cf86b34f03ebf9e0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser