samara-sts.ru

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

This reading of samara-sts.ru was taken 4d ago

samara-sts.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting samara-sts.ru 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 samara-sts.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Registered withACTIVE-RU
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 19:20 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 samara-sts.ru actually stands on - every host below is a signed observation
samara-sts.ru
A / AAAA
37.187.202.101176.31.176.75
unattributedserves the site
NS
ns2.expired.active.domainsns1.expired.active.domains
active.domainsanswers its DNS

DNS Records

A 2

  • 37.187.202.101
  • 176.31.176.75

TXT 2

  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;
  • v=spf1 ip4:127.0.0.1 -all

NS 2

  • ns2.expired.active.domains
  • ns1.expired.active.domains

SOA 1

  • expired.active.domains support.active.domains

MCP_RECORDS 2

  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;
  • v=spf1 ip4:127.0.0.1 -all

DMARC_RECORDS 2

  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

BIMI_RECORDS 2

  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;
  • v=spf1 ip4:127.0.0.1 -all

MTA_STS_RECORDS 2

  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

TLS Certificates (0)

None.

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_5eaf63c2d4b5e939
Output Hash
8cc0040af5f418f2405909b8e02a42ea98ecd706a67d5e1ac65db4e364d057a3
Signature
ed25519:88ef73e3e7d2b30d543c549eca340597d6a984a25dde48bdf4790af7f0110eb018e1549ac9d894ba8c46db80421d2943c77b1c3e59f8890f7f3f3c363a764d04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT45,942 material changesacross 44,053 domains · 24h to ~2h ago · +1,860 vs yesterdayROTATION64 domains moved DNS from koaladns.com to magpiedns.com, 63 moved backa rotation loop, not a migration · 24hNOW491 curated domains not reachablelast probe, steadySITE ERRORS36,522 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,165 sites429 rate-limit / 403 bot-block, a posture signal