CONTINUOUS INTERNET TELEMETRY24H DRIFT27 material changesacross 1 domains · -1,609 vs yesterdayNOW60,294 curated domains not answering+45,871 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT27 material changesacross 1 domains · -1,609 vs yesterdayNOW60,294 curated domains not answering+45,871 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT27 material changesacross 1 domains · -1,609 vs yesterdayNOW60,294 curated domains not answering+45,871 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

zensar.com

Observed 2026-07-15T09:46:19.724Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Registered withNetwork Solutions, LLC
Also usesGoogle Search Console
5 subdomains · consulting
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat zensar.com actually stands on - every host below is a signed observation
zensar.com
A / AAAA
4.224.112.29
Cloudflareserves the site
NS
ns1.zensar.comns2.zensar.com
zensar.comanswers its DNS
MX
mx1.hc1447-79.ap.iphmx.commx2.hc1447-79.ap.iphmx.com
iphmx.comreceives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.zensar.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1767 ms
DNS resolutionNOERROR
Redirect chain
https://www.zensar.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

  • 4.224.112.29

MX 2

  • 10mx1.hc1447-79.ap.iphmx.com
  • 10mx2.hc1447-79.ap.iphmx.com

TXT 14

  • MS=ms11308332
  • duo_sso_verification=ZaNpXvktGsHYyILUov3eVyjWZ1BDhnFTt9TIFyjWIvNZztRbeTsn28Un5PFPcruR
  • pardot1099692=5544038aef9a82885d6db652940517dd3f3eef5c7a15694538c9af938ffe2444
  • sending_domain884993=57ad6bc73a7e1f249d519cbe0e6f9544974718a98dacba176db428f2b3a5adff
  • pardot1099692=ed72b79a0dacb419e6cde864504149789281da08372fb05dbbe9bb7132e764fa
  • google-site-verification=4Bg-zHgjAfawJTDE2JQRJF91eYjQ74OJAUWGtMrhQso
  • tIJgpfzo8uPl6U4dV59Txe/QiLhqk/oBnBxOg5Jds3v9iRyy4oD/hkTK8NRwL25iUjg6s8TDu9tEsiU1tTl4Dg==
  • google-gws-recovery-domain-verification=51877950
  • jamf-site-verification=nQDo4lN_0VhTCvZj9SF2YA
  • _ts09jozw5budop0pcs6j4kuz77qovhr

NS 2

  • ns1.zensar.com
  • ns2.zensar.com

SOA 1

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

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

Ed25519 Receipt

Receipt ID
a839a9aa-49a0-4e62-87d3-6b423ed6a77a
Output Hash
c777c8ae14054494cfc09ad12bd263f160c91c4102ba3c0b5317029cabe2a068
Signature
ed25519:eea01d6fbc089a6c667133e974d61d3b17d83eff580d3ba64e88f4181be63d71809b0e1521e205e6a8ff67de54a5de4b376be5a9bba530c20fbdbfa0d084fa0f
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser