asp24.ru
Observed Aug 11, 2026, 05:07 UTC (7d ago). Every field below was attested with an Ed25519 signature at scan time.
asp24.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting asp24.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 asp24.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.Steady. No change on record for asp24.ru in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 1
217.174.105.109
MX 1
10mx.yandex.net
TXT 3
mailru-verification: f7c683cd6409fc41google-site-verification=EoVV8Pzks4HYeOLmTr2BolqM10Le0LCHGbmuRulOsAQv=spf1 redirect=_spf.yandex.net
NS 2
ns2.1telecom.runs.1telecom.ru
SOA 1
ns.1telecom.ru hostmaster.1system.ru
MCP_RECORDS 3
v=spf1 redirect=_spf.yandex.netmailru-verification: f7c683cd6409fc41google-site-verification=EoVV8Pzks4HYeOLmTr2BolqM10Le0LCHGbmuRulOsAQ
DMARC_RECORDS 1
v=DMARC1; p=none; rua=mailto:postmaster@asp24.ru
BIMI_RECORDS 3
google-site-verification=EoVV8Pzks4HYeOLmTr2BolqM10Le0LCHGbmuRulOsAQv=spf1 redirect=_spf.yandex.netmailru-verification: f7c683cd6409fc41
MTA_STS_RECORDS 3
mailru-verification: f7c683cd6409fc41google-site-verification=EoVV8Pzks4HYeOLmTr2BolqM10Le0LCHGbmuRulOsAQv=spf1 redirect=_spf.yandex.net
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
www.asp24.ru |
C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R6 AlphaSSL CA 2025 | Sat, 28 Nov 2026 09:08:46 +0000 |
GlobalSign GCC R6 AlphaSSL CA 2025 |
2.5.4.11=GlobalSign Root CA - R6, O=GlobalSign, CN=GlobalSign | Fri, 21 May 2027 00:00:00 +0000 |
GlobalSign |
2.5.4.11=GlobalSign Root CA - R6, O=GlobalSign, CN=GlobalSign | Sun, 10 Dec 2034 00:00:00 +0000 |
Subdomains (1)
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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_5bc1b4491b452d19- Output Hash
6d3d8d92a8a4255af938a5ce92e184eb75d7b4cd78f794644ac4b52aa1194f73- Signature
ed25519:64f0fb404d618313bfb0c6f0ce09f8745f9f14d7ef2d4538eba01bb4353c3b312b7eefdd6aa3286b95953b6fef3ee43f309f13241f03b1d0d31bf441df36430e- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast