CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · 24h to ~40m agoSHIFT21 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,162 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,262 sites429 rate-limit / 403 bot-block, a posture signal

rtl-adalliance.com

Observed Jul 26, 2026, 06:29 UTC (9d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of rtl-adalliance.com was taken 9d ago

rtl-adalliance.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting rtl-adalliance.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 rtl-adalliance.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-03 23: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 rtl-adalliance.com actually stands on - every host below is a signed observation
rtl-adalliance.com
A / AAAA
54.37.211.165
unattributedserves the site
NS
ns1.eurodns.comns2.eurodns.comns3.eurodns.comns4.eurodns.com
eurodns.comanswers its DNS
TLS
rtl-adalliance.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 54.37.211.165

MX 1

  • 0

TXT 6

  • v=spf1 -all
  • d365mktkey=IFy9qhObxXDmW9UaVDqOxmgc45wdMe7K8kVB6qyaLDcx
  • v=DMARC1; p=reject
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 4

  • ns1.eurodns.com
  • ns2.eurodns.com
  • ns3.eurodns.com
  • ns4.eurodns.com

SOA 1

  • ns1.eurodns.com hostmaster.eurodns.com

TLS Certificates (3)

Common NameIssuerExpires
rtl-adalliance.com C=US, O=Let's Encrypt, CN=YR1 Wed, 14 Oct 2026 07:26:34 +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 (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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_c02348f26d15afb5
Output Hash
e2f50d027a27e0d029b949e17b041b09811c0846c55bee27188fe242c21b37c7
Signature
ed25519:3a7185d26ad10579ffd8169df28f3946f67485d67637e914f0d780eefd4c2ad08ceba2551c2beaef24210c43bc8d9ff67d59e3d972a3d189b1ba88b88e634504
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser