CONTINUOUS INTERNET TELEMETRY24H DRIFT1,856 material changesacross 1,677 domains · -103 vs yesterdayDNS DRIFT21 domains changed DNS providertop destination parity.domains · +2 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT2 domains switched issuing CA24hNOW3,453 curated domains not answeringlast probe, steadyERRORS8,546 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,316 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT1,856 material changesacross 1,677 domains · -103 vs yesterdayDNS DRIFT21 domains changed DNS providertop destination parity.domains · +2 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT2 domains switched issuing CA24hNOW3,453 curated domains not answeringlast probe, steadyERRORS8,546 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,316 throttled or blocked our scanner429 rate-limit / 403 bot-block

hallmark.com

Observed 2026-07-14T11:07:48.869Z (16h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Registered withNom-iq Ltd. dba COM LAUDE
Also usesAtlassianGoogle Search ConsoleDocuSignFacebook/MetaFigmaMiroDocker
11 subdomains · tranco_20k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat hallmark.com actually stands on - every host below is a signed observation
hallmark.com
A / AAAA
23.205.249.20723.205.249.183
Cloudflareserves the site
NS
auth00.ns.uu.netns2.hallmark.comauth100.ns.uu.netns1.hallmark.com
uu.net + hallmark.comanswers its DNS
MX
hallmark-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.hallmark.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/3
TLS issuernot observed
Behind Cloudflareyes
Response time245 ms
DNS resolutionNOERROR
Redirect chain
https://www.hallmark.com/

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

DNS Records

A 2

  • 23.205.249.207
  • 23.205.249.183

MX 1

  • 0hallmark-com.mail.protection.outlook.com

TXT 44

  • 86506ba9-bb12-46fd-840d-f9f9ed0ab226
  • klaviyo-site-verification=UfnqXE
  • llp8qqxwddsrf4t38mnh1jqwp9dqb9np
  • atlassian-domain-verification=ziiGsHvXJGYqcAyAw1RdxqksmNyE3vfRXvRX4UyL8Yt7+14k2jmWA/8xBS1To+b8
  • apple-domain-verification=yfxBJu7cC9FxAjR4
  • 2rbypjhl9tshswsrlfd6flqdc2xd0xqs
  • google-site-verification=NOzWw2wWG0MLL8kncjLZvsAyHoedrAcM--SAwOcu4Rw
  • globalsign-domain-verification=11465675D5E7C45894B18A0B6A34E920
  • docusign=c880f5ab-9af7-4922-9fae-85b8979542c5
  • canva-site-verification=LrzlUo_01R-V9dBOFE6dcQ

NS 4

  • auth00.ns.uu.net
  • ns2.hallmark.com
  • auth100.ns.uu.net
  • ns1.hallmark.com

SOA 1

  • ns1.hallmark.com please_set_email.absolutely.nowhere

TLS Certificates (0)

None.

Subdomains (11)

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

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

Ed25519 Receipt

Receipt ID
5a0b3a9c-3550-4cae-8113-c02fa364ae5b
Output Hash
45f8e575158526ab087014df65bf87c5e49649f0c00f070f5f8743d4c3cf9eb2
Signature
ed25519:327387f01143809a02ef7cc126e3abde8c991e0030baa22b7d363788224e00c5eeb322a7ae27b2e7e6c9fe280c8177bc5595e7d599e86568258746a2b0790e04
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser