CONTINUOUS INTERNET TELEMETRY24H DRIFT8,763 material changesacross 8,372 domains · 24h to ~2h ago · -32,097 vs yesterdayNOW563 curated domains not reachablelast probe, steadySITE ERRORS34,264 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,299 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

userecho.ru

Observed Aug 2, 2026, 22:20 UTC (1h 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
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 22: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 userecho.ru actually stands on - every host below is a signed observation
userecho.ru
A / AAAA
77.223.108.162
unattributedserves the site
NS
ns.eu2.stamul.comns.us4.stamul.comns.ru1.userecho.ru
stamul.com + userecho.ruanswers its DNS
MX
mx.yandex.net
yandex.netreceives its email
TLS
*.userecho.ru
Let's Encryptissued its certificate

DNS Records

A 1

  • 77.223.108.162

MX 1

  • 10mx.yandex.net

TXT 2

  • v=spf1 include:smtp.userecho.com redirect=_spf.yandex.net
  • yandex-verification: 28f9d9668cf23961

NS 3

  • ns.eu2.stamul.com
  • ns.us4.stamul.com
  • ns.ru1.userecho.ru

SOA 1

  • ns.ru1.userecho.ru info.userecho.ru

MCP_RECORDS 1

  • v=spf1 a mx include:smtp.userecho.com ~all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100; rua=mailto:info@userecho.com;

BIMI_RECORDS 1

  • v=spf1 a mx include:smtp.userecho.com ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx include:smtp.userecho.com ~all

TLS Certificates (4)

Common NameIssuerExpires
*.userecho.ru C=US, O=Let's Encrypt, CN=YE1 Sun, 06 Sep 2026 18:10:20 +0000
YE1 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 (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_b1bcc02347f47c47
Output Hash
0fc7ea2391871b158e53d293f0781407596f8f11f3c361cb3d06178a4e2962e1
Signature
ed25519:91081906c782b17bd5aaaa9b40abac93c737b12e9ee8642b7b7dcfe9b43f2ee8bf4eb81f75bca013aa04a92f9371808d5ce63ca5fa78fdc08489a3a4639cbc09
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser