reitor.ru

Observed Aug 16, 2026, 18:05 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of reitor.ru was taken 1d ago

reitor.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting reitor.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 reitor.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.

Verify this receipt yourself + Watch this domain

Not responding

Signed observation on record.

domcop

Every line above is a signed observation. Check the math at the bottom of the page.

DRIFT

Steady. No change on record for reitor.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.

INFRASTRUCTURE MAPwhat reitor.ru actually stands on - every host below is a signed observation

reitor.ru

A / AAAA

176.31.179.19137.187.83.72

unattributedserves the site

dns1.ru-tld.rudns2.ru-tld.ru

ru-tld.ruanswers its DNS

DNS Records

A 2

176.31.179.191
37.187.83.72

TXT 3

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

NS 2

dns1.ru-tld.ru
dns2.ru-tld.ru

SOA 1

dns.ru-tld.ru support.ru-tld.ru

MCP_RECORDS 3

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

DMARC_RECORDS 3

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

BIMI_RECORDS 3

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

MTA_STS_RECORDS 3

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

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-17 18:06 UTC

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

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_002e6b7441877ef3
Output Hash: 49f9c4caaa6228c8409f9d680df369949db4aab0665f729b2e34ccaaed64ece0
Signature: ed25519:993bbc1a20f9d5d0e5a430151460354bcdf89780b467d126a6ba753eeeaed441d78488888c996f31b4fbb5ff972486c9e52ac4c9f9b3d084ed336da59dcd4707
Public Key: ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent: (genesis)
Plane: fast

Verify this in your browser

Permalink: https://domaindrift.io/t/reitor.ru