CONTINUOUS INTERNET TELEMETRY24H DRIFT33,450 material changesacross 32,285 domains · 24h to ~10h ago · -4,572 vs yesterdayROTATION56 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW549 curated domains not reachablelast probe, steadySITE ERRORS33,824 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,662 sites429 rate-limit / 403 bot-block, a posture signal

tourister.ru

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

This reading of tourister.ru was taken 4d ago

tourister.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting tourister.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 tourister.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Responding, no home page
Runs onInternet-Pro
Secured byGlobalSign
tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 08:52 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 tourister.ru actually stands on - every host below is a signed observation
tourister.ru
A / AAAA
45.86.39.72
Internet-Proserves the site
NS
ns1.netangels.runs2.netangels.runs3.netangels.runs4.netangels.ru
netangels.ruanswers its DNS
MX
mail.tourister.ru
tourister.rureceives its email
TLS
*.tourister.ru
GlobalSign nv-saissued its certificate

DNS Records

A 1

  • 45.86.39.72

MX 1

  • 10mail.tourister.ru

TXT 4

  • v=spf1 +mx a:tourister.ru ip4:91.201.53.114 ip4:193.107.236.22 ip4:91.201.53.159 ip4:45.86.39.106 include:spf.unisender.com ~all
  • mailru-verification: 7644448beabda713
  • yandex-verification: 48c62158e391336f
  • _globalsign-domain-verification=zQCNMgL1_nJVYmU2TgNvIZeebk5FjS2BbxnOzpNTOg

NS 4

  • ns1.netangels.ru
  • ns2.netangels.ru
  • ns3.netangels.ru
  • ns4.netangels.ru

SOA 1

  • ns1.netangels.ru hostmaster.netangels.ru

MCP_RECORDS 4

  • v=spf1 +mx a:tourister.ru ip4:91.201.53.114 ip4:193.107.236.22 ip4:91.201.53.159 ip4:45.86.39.106 include:spf.unisender.com ~all
  • mailru-verification: 7644448beabda713
  • yandex-verification: 48c62158e391336f
  • _globalsign-domain-verification=zQCNMgL1_nJVYmU2TgNvIZeebk5FjS2BbxnOzpNTOg

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine; sp=quarantine; pct=100; fo=1; rua=mailto:report-rua@tourister.ru;

BIMI_RECORDS 4

  • v=spf1 +mx a:tourister.ru ip4:91.201.53.114 ip4:193.107.236.22 ip4:91.201.53.159 ip4:45.86.39.106 include:spf.unisender.com ~all
  • mailru-verification: 7644448beabda713
  • yandex-verification: 48c62158e391336f
  • _globalsign-domain-verification=zQCNMgL1_nJVYmU2TgNvIZeebk5FjS2BbxnOzpNTOg

MTA_STS_RECORDS 4

  • v=spf1 +mx a:tourister.ru ip4:91.201.53.114 ip4:193.107.236.22 ip4:91.201.53.159 ip4:45.86.39.106 include:spf.unisender.com ~all
  • mailru-verification: 7644448beabda713
  • yandex-verification: 48c62158e391336f
  • _globalsign-domain-verification=zQCNMgL1_nJVYmU2TgNvIZeebk5FjS2BbxnOzpNTOg

TLS Certificates (2)

Common NameIssuerExpires
*.tourister.ru C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R6 AlphaSSL CA 2025 Wed, 06 Jan 2027 05:47:16 +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

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_fb368bc7c53be044
Output Hash
7f61696b9613dbe8bb1373b5a85558d894d85c49b0a90607c5c28cdfb5a3a6ce
Signature
ed25519:531e5e3c183eb3b07ca83eb877e06330d39a1b9f6c21fe92ee654bc5a7f8895a6c41b7eedb69d7a0079fcb8f931af8194ea27ef2a7eedb30660f739097aa870c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser