CONTINUOUS INTERNET TELEMETRY24H DRIFT3,027 material changesacross 2,680 domains · -371 vs yesterdayDNS DRIFT25 domains changed DNS providertop destination cloudflare.com · -2 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,307 curated domains not answering-6,411 vs yesterdayERRORS10,958 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,027 material changesacross 2,680 domains · -371 vs yesterdayDNS DRIFT25 domains changed DNS providertop destination cloudflare.com · -2 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,307 curated domains not answering-6,411 vs yesterdayERRORS10,958 responded with an errorlast probe · 5xx / 404 / 429 / 403

kay.com

Observed 2026-07-12T13:13:10.527Z (23h ago). Every field below was attested with an Ed25519 signature at scan time.

Guarded by a firewall
Runs onCloudflare
Email byMimecast
Also usesGoogle Search ConsoleFacebook/Meta
5 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat kay.com actually stands on - every host below is a signed observation
kay.com
A / AAAA
23.211.124.20823.211.124.207
Cloudflareserves the site
NS
a4-64.akam.neta22-66.akam.neta3-67.akam.neta1-183.akam.net+2 more
akam.netanswers its DNS
MX
us-smtp-inbound-2.mimecast.comus-smtp-inbound-1.mimecast.com
Mimecastreceives its email

HTTPS probe

bot_blocked Blocked our probe (WAF / bot protection) 403 blocked by cloudflare - bot protection active
HTTP status403
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time163 ms
DNS resolutionNOERROR

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.211.124.208
  • 23.211.124.207

MX 2

  • 10us-smtp-inbound-2.mimecast.com
  • 10us-smtp-inbound-1.mimecast.com

TXT 10

  • globalsign-domain-verification=cfa58eafa28b9c93a8e0442b6fa97979
  • globalsign-domain-verification=ED8CCE730C25CAC9F98BE637C3CC2B1D
  • google-site-verification=hdA8XTDrw0OyfQXaX10VZYoN6FuIuVISOdq4FM8RF90
  • facebook-domain-verification=yepenx397susjlj6txbh9krxg8x8px
  • amazonses:JB4WbGU8LimGdL/Ok0cyLa3pM5jBinC/3ml2GtD9b3k=
  • google-site-verification=INxq5rA4vhHdMcELgn1QxNDvBi_Xy6ejGe-_rABNzqc
  • amazonses:TSMW2Wroo/AerlEE08pVbYKVajL/xfUIAed3peFkE5w=
  • v=spf1 include:_netblocks.mimecast.com include:aspmx.sailthru.com ~all
  • MS=ms32180592
  • v=DMARC1; p=quarantine; rua=mailto:ed800b049e7f095@rep.dmarcanalyzer.com; ruf=mailto:ed800b049e7f095@for.dmarcanalyzer.com; fo=1;

NS 6

  • a4-64.akam.net
  • a22-66.akam.net
  • a3-67.akam.net
  • a1-183.akam.net
  • a13-64.akam.net
  • a14-65.akam.net

SOA 1

  • a1-183.akam.net hostmaster.akamai.com

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

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

Ed25519 Receipt

Receipt ID
0240463b-c2ee-4d4f-a511-a2b98ded4045
Output Hash
7c3ad7efe63292c6fe6bb2e60cbc5dba9425133c6d3bf6db674bf7c44b6c6606
Signature
ed25519:65199340da041acf0f343787c47593258ca3418ab7e401dd7de834a9ad1d5cfc3fbebb1674238fb39d2abdcf5d375fbaecea78a1a2f6f42c18d444a36c6bec01
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser