CONTINUOUS INTERNET TELEMETRY24H DRIFT3,169 material changesacross 2,744 domains · -229 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -3 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,319 curated domains not answering-6,399 vs yesterdayERRORS10,956 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,169 material changesacross 2,744 domains · -229 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -3 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,319 curated domains not answering-6,399 vs yesterdayERRORS10,956 responded with an errorlast probe · 5xx / 404 / 429 / 403

vishay.com

Observed 2026-07-12T17:20:16.662Z (11h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Registered withCSC Corporate Domains, Inc.
Also usesGoogle Search ConsoleDocuSign
manufacturing
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat vishay.com actually stands on - every host below is a signed observation
vishay.com
A / AAAA
198.24.10.102
Cloudflareserves the site
NS
ns4-04.azure-dns.infons3-04.azure-dns.orgns2-04.azure-dns.netns1-04.azure-dns.com
azure-dns.info + azure-dns.org + moreanswers its DNS
MX
vishay-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

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

  • 198.24.10.102

MX 1

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

TXT 13

  • _w5a87jwpwx7ep9fa3jt1kwkgld7y2sp
  • ibmid=bd97f6e6-e3e8-48ea-97fa-a095462dcd5f
  • google-site-verification=Hmixw_zq2uOkYj__1XSqYMeC1H5HmmyJ9WCH4Ao3ISM
  • v=spf1 ip4:193.228.122.60 ip4:193.228.122.61 include:spf.protection.outlook.com include:spf2.vishay.com -all
  • 5eorAukxs2G9N5tnSkcXIl12IsIbJTJl08iRAuSWcGunQHgQQ+RmcIXt2Hb4eUp03WNgkjp5xbcyHsGJEYxCJQ==
  • 7mhbcfeiop5mukhlev3bon4oup
  • teamviewer-sso-verification=cb2e59092a9c4e83af56c890c9e6b8a8
  • apple-domain-verification=wJH4RsmRM03IcAhS
  • onetrust-domain-verification=960d5d86bfd64b88a13b54cc4ba2f7e3
  • docusign=83605fdc-42b5-4042-a788-b462af2a8bab

NS 4

  • ns4-04.azure-dns.info
  • ns3-04.azure-dns.org
  • ns2-04.azure-dns.net
  • ns1-04.azure-dns.com

SOA 1

  • ns1-04.azure-dns.com hostmaster.vishay.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 vishay.com. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
b1fb5641-2340-4199-8149-d2cbc5328a83
Output Hash
c2fdf85341009f6f16524fceaa93f5f70df1518e4fd55cb5485b4e12c254bbb8
Signature
ed25519:988fd237e25807b4cfe6e67f409320aeaa89e5d01aab6a7c3bf6e40076fc7e27c0c6f7c0dde0814244606c1e27432a6854c505c2c33636bf36cb7e830f68ca05
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser