vats-on.ru
Observed Aug 3, 2026, 10:07 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.
vats-on.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vats-on.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 vats-on.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.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.
DNS Records
A 1
176.57.67.113
MX 1
10mx.yandex.net
TXT 1
v=spf1 ip4:89.17.45.196 a:mta-01.vats-on.ru include:_spf.yandex.net -all
NS 6
ns1-04.azure-dns.comns2-04.azure-dns.netns3-04.azure-dns.orgns4-04.azure-dns.infons1.yandexcloud.netns2.yandexcloud.net
SOA 1
ns1-04.azure-dns.com azuredns-hostmaster.microsoft.com
CAA 8
iodef "mailto:caa.report@vats-on.ru"issuemail ";"issuevmc ";"issue "letsencrypt.org"issuewild "letsencrypt.org; accounturi=https://acme-staging-v02.api.letsencrypt.org/acme/acct/1943067; validationmethods=dns-01"issuewild "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/30990147; validationmethods=dns-01"issuewild "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/742543507; validationmethods=dns-01"issuewild "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/742550987; validationmethods=dns-01"
MCP_RECORDS 1
v=spf1 -all
DMARC_RECORDS 1
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; fo=1; rua=mailto:dmarc.report@vats-on.ru; ruf=mailto:dmarc.report@vats-on.ru
BIMI_RECORDS 1
v=spf1 -all
MTA_STS_RECORDS 1
v=spf1 -all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
vats-on.ru |
C=US, O=Let's Encrypt, CN=YR1 | Thu, 10 Sep 2026 06:53:37 +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.
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 receiptEd25519 Receipt
- Receipt ID
rcpt_81479e16772e2543- Output Hash
185471408342a8a7a9a10ec7c64846ea98e870920c435fa3aaf6228c97640b1c- Signature
ed25519:3eb5a083033aa60fa962c3986989319c55cdf9a7f45a543ca093bc8e51a12ecf2eed4244ff9f92491a612d2a75100d3fb58316ebfcd2d4bae52b3825ffedef0c- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast