CONTINUOUS INTERNET TELEMETRY24H DRIFT337 material changesacross 291 domains · -321 vs yesterdayCERT DRIFT3 domains switched issuing CA24h · +1 vs yesterdayNOW3,442 curated domains not answering+613 vs yesterdayERRORS22,646 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED62,942 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT337 material changesacross 291 domains · -321 vs yesterdayCERT DRIFT3 domains switched issuing CA24h · +1 vs yesterdayNOW3,442 curated domains not answering+613 vs yesterdayERRORS22,646 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED62,942 throttled or blocked our scanner429 rate-limit / 403 bot-block

russianpost.ru

Observed Jul 18, 2026, 12:43 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.

Not responding
Runs onJSC _Russian Post_
Also usesGoogle Search Console
tranco_5k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat russianpost.ru actually stands on - every host below is a signed observation
russianpost.ru
A / AAAA
91.215.36.177
JSC _Russian Post_serves the site
NS
d01ns1.russianpost.rud02ns1.russianpost.rur00ns2.russianpost.ru
russianpost.ruanswers its DNS
MX
R00EXEDGE01.main.russianpost.rusmart1.russianpost.rudc-smart1.russianpost.rur00smtpapp01.russianpost.ru+8 more
russianpost.rureceives its email

DNS Records

A 1

  • 91.215.36.177

MX 12

  • 20R00EXEDGE01.main.russianpost.ru
  • 90smart1.russianpost.ru
  • 90dc-smart1.russianpost.ru
  • 90r00smtpapp01.russianpost.ru
  • 90d01smtpapp02.russianpost.ru
  • 20D02EXEDGE02.main.russianpost.ru
  • 90r00smtpapp02.russianpost.ru
  • 20D02EXEDGE01.main.russianpost.ru
  • 90d01smtpapp01.russianpost.ru
  • 20D02EXEDGE03.main.russianpost.ru

TXT 9

  • _globalsign-domain-verification=iFLnc4Xkw2QkiSsjMcO1lJkev6IYluUs6rxtmg2nUh
  • v=spf1 ip4:91.215.36.209 ip4:91.215.36.210 ip4:91.215.36.211 ip4:91.215.39.209 ip4:91.215.39.210 ip4:91.215.39.211 ip4:91.215.36.115 ip4:91.215.37.115 ip4:91.215.36.96/30 ip4:91.215.37.96/30 ip4:91.215.36.227/29 ip4:91.215.39.227/29 ip4:91.215.37.211 -all
  • google-site-verification=WqARxTdYWJZJlBrUk3hbeVsaU0FV1j4dQnrRWfZ0PlQ
  • mailru-verification: f63e8ad4b44e066a
  • _globalsign-domain-verification=1ARSgJkfqHEv52K1JtkjbmORemOWl3Izgs3uef9qn-
  • yandex-verification: a97035a6baf74a72
  • u7xjTbcoqmxFc7bkm4ZdSKumFwlkjcv8u32mxclknMaqxf
  • google-site-verification=mAu0YsSSNSdIVibX3Fioo2j1X6IPFAV21JEwTqXm1o0
  • v=DMARC1; p=quarantine; pct=100; sp=none; rua=mailto:feedbackloop@russianpost.ru; adkim=r; aspf=r;

NS 3

  • d01ns1.russianpost.ru
  • d02ns1.russianpost.ru
  • r00ns2.russianpost.ru

SOA 1

  • r00ns1.russianpost.ru postmaster.russianpost.ru

TLS Certificates (0)

None.

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

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for russianpost.ru. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for russianpost.ru <a href="https://domaindrift.io/t/russianpost.ru"> <img src="https://domaindrift.io/badge/russianpost.ru.svg" width="300" height="64" alt="DomainDrift signed observations for russianpost.ru"> </a>

Ed25519 Receipt

Receipt ID
cdf48176-1672-4404-8389-b6dc6fab8bd6
Output Hash
df0c9ab013bcda4ba09799ff6f7dea2f509482d8b6e588079a041146be944c0e
Signature
ed25519:e7dfb349b2b29d69f7ffcacce655dd66a0905b4f45e40e545e38e5ad25ef5b4ae0c19a4fb5919ebddab5e0b0c3939e9e9e771c4dc221719e71128e4c72691d0a
Public Key
ed25519:178c3bd0f57d9d64b83cc4630753381e1a465005a2bbba3d032371f24af0bfd8
Parent
(genesis)
Plane
fast
Verify this in your browser