CONTINUOUS INTERNET TELEMETRY24H DRIFT69 material changesacross 42 domains · -1,567 vs yesterdayNOW3,482 curated domains not answering-10,941 vs yesterdayERRORS8,521 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT69 material changesacross 42 domains · -1,567 vs yesterdayNOW3,482 curated domains not answering-10,941 vs yesterdayERRORS8,521 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT69 material changesacross 42 domains · -1,567 vs yesterdayNOW3,482 curated domains not answering-10,941 vs yesterdayERRORS8,521 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

licard.com

Observed 2026-07-14T20:20:29.945Z (2d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Registered withRegional Network Information Center, JSC dba RU-CENTER
DNSSEC on · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat licard.com actually stands on - every host below is a signed observation
licard.com
A / AAAA
91.234.16.49
Cloudflareserves the site
NS
ns2.licard.runs3.licard.ru
licard.ruanswers its DNS
MX
extmail8.licard.commx2.atmosphere.facct.rumsk01-smtprelay02.licard.commx1.atmosphere.facct.ru+4 more
licard.com + facct.ru + morereceives its email

HTTPS probe

redirect Redirecting (3xx) 302 → https://licard.com/owa/
HTTP status302
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1171 ms
DNS resolutionNOERROR
Redirect chain
https://licard.com/owa/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 91.234.16.49

MX 8

  • 15extmail8.licard.com
  • 9mx2.atmosphere.facct.ru
  • 80msk01-smtprelay02.licard.com
  • 9mx1.atmosphere.facct.ru
  • 50smtprelay.licard.ru
  • 16extmail5.licard.com
  • 17extmail6.licard.com
  • 15extmail7.licard.com

TXT 9

  • yandex-verification: 582d1709cf3debb8
  • 9DTsPbAoLW6bgvTS6NKUKx5pMYoGl4QygEAzt8MJeaBdQdZRMgj12YzLAkFt8otJKio7VjzQpLyxLS6L1KwOW5SEh0MD0KNshp3z
  • mailru-verification: 6372abbda5e768b5
  • v=spf1 +a +mx ~all
  • asap-site-verification-29e207b3-1dd3-4a61-8d45-a863eb02a918
  • yandex-verification: 3ccfcad54072589e
  • mailru-verification: 5bddcd7ddc3f71b5
  • v=DMARC1; p=reject; rua=mailto:dmarc@licard.com
  • v=DNSSEC1; (detected)

NS 2

  • ns2.licard.ru
  • ns3.licard.ru

SOA 1

  • ns2.licard.ru admin.licard.ru

TLS Certificates (0)

None.

Subdomains (5)

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 licard.com. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
5b93e087-dc6b-421f-92ec-e157ead6e7eb
Output Hash
2d29da17ea6be92f46d6285621a9ae298adc9ff597bb213c0e886d70614907de
Signature
ed25519:aff4a78725655096647aa1895533d2b8c8badeed1ec08b426e71f274afcdb984e34c8b1608656cede62dcb43eafedbf68c040fa53a6b8240aee56f6090cd760f
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser