CONTINUOUS INTERNET TELEMETRY24H DRIFT644 material changesacross 547 domains · -14 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination kirklanddc.comCERT DRIFT2 domains switched issuing CA24hNOW2,867 curated domains not answeringlast probe, steadyERRORS19,104 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED50,556 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT644 material changesacross 547 domains · -14 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination kirklanddc.comCERT DRIFT2 domains switched issuing CA24hNOW2,867 curated domains not answeringlast probe, steadyERRORS19,104 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED50,556 throttled or blocked our scanner429 rate-limit / 403 bot-block

yay.com

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

Up right now
Runs onCloudflare
Email byGoogle Workspace
Registered withNameCamp Limited
Also usesGoogle Search ConsoleFacebook/MetaHubSpot
16 subdomains · tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat yay.com actually stands on - every host below is a signed observation
yay.com
A / AAAA
34.49.72.177
Cloudflareserves the site
NS
ns-cloud-c2.googledomains.comns-cloud-c3.googledomains.comns-cloud-c4.googledomains.comns-cloud-c1.googledomains.com
googledomains.comanswers its DNS
MX
alt2.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email

HTTPS probe

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

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

DNS Records

A 1

  • 34.49.72.177

MX 5

  • 5alt2.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 1aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 10alt3.aspmx.l.google.com

TXT 10

  • google-site-verification=_GSK8SuX9d-o1zitmDV-_fmo6XRdnmmQfRYBxU5MY64
  • apple-domain-verification=sm6nY93g3WL2VbNK
  • v=spf1 include:spf.mandrillapp.com include:_spf.google.com include:mail.zendesk.com ~all
  • jetbrains-domain-verification=8na9xe85qz0w5u9txvhk33ask
  • TAILSCALE-6AIkaxe5oMYNRPs2gGs7
  • MS=ms39091327
  • facebook-domain-verification=mtoy9gpbhibkilmiavv3wpg2ah7jhu
  • hubspot-developer-verification=YjcwNjQyNDEtODk0MS00OWNlLWFhOTEtZTE0Y2QyOTRiMzBm
  • v=DMARC1; p=reject; rua=mailto:dmarc@yay.com
  • v=DKIM1; (detected)

NS 4

  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.com
  • ns-cloud-c1.googledomains.com

SOA 1

  • ns-cloud-c1.googledomains.com cloud-dns-hostmaster.google.com

TLS Certificates (0)

None.

Subdomains (16)

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

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

Ed25519 Receipt

Receipt ID
231814ee-bad3-4bd7-87a8-9721d72734b8
Output Hash
f5597729a6c755ab8f25cfbdb5f9fcc24d3eab2be5552f800ba8ca57dd644300
Signature
ed25519:faecf352e87d73a91aadef8cb5166c4fe7bc950f2adc9837dba638f07b985b3e66492241b597e2ff0bcc37b5672c0d609a83b38f4b772d636510162f6789910c
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser