vishay.com

Checked 22 October 2026, 11:22 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 3 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-09-09

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
10 September 1995
Last changed
5 September 2026
Expires
9 September 2027
Status
client transfer prohibited
Registry nameservers
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-09-09 #3
    The registration is valid until 2027-09-09 (321 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NS in the zone
ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-04.azure-dns.com13.107.236.4 2603:1061:0:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.4 2603:1061:0:700::4
ns2-04.azure-dns.net150.171.21.4 2620:1ec:8ec:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-04.azure-dns.org204.14.183.4 2a01:111:4000:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-04.azure-dns.info208.84.5.4 2620:1ec:bda:700::4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-04.azure-dns.com 13.107.236.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-04.azure-dns.com 2603:1061:0:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 150.171.21.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 2620:1ec:8ec:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 204.14.183.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 2a01:111:4000:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-04.azure-dns.info 208.84.5.4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-04.azure-dns.info 2620:1ec:bda:700::4NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2017022082 · primary ns1-04.azure-dns.com

Found

Primary (MNAME)
ns1-04.azure-dns.com
Contact (RNAME)
hostmaster.vishay.com
Serial
2017022082
Refresh / retry
1200 s / 3600 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1-04.azure-dns.com (13.107.236.4)2017022082
ns1-04.azure-dns.com (2603:1061:0:700::4)2017022082
ns2-04.azure-dns.net (150.171.21.4)2017022082
ns2-04.azure-dns.net (2620:1ec:8ec:700::4)2017022082
ns3-04.azure-dns.org (204.14.183.4)2017022082
ns3-04.azure-dns.org (2a01:111:4000:700::4)2017022082
ns4-04.azure-dns.info (208.84.5.4)2017022082
ns4-04.azure-dns.info (2620:1ec:bda:700::4)2017022082

Checks

  • ✓ Serial 2017022082 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 20m. Current values: refresh 20m, retry 1h, expire 28d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-04.azure-dns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@vishay.com #25
    The SOA RNAME hostmaster.vishay.com means hostmaster@vishay.com.
  • ✓ Date-based serial #26
    The serial 2017022082 follows the YYYYMMDDnn convention (2017-02-20).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

20 records at the apex

Found

Read from
13.107.236.4:53
TypeValueTTL
SOAns1-04.azure-dns.com. hostmaster.vishay.com. 2017022082 1200 3600 2419200 36003600
NSns1-04.azure-dns.com.2
NSns2-04.azure-dns.net.2
NSns3-04.azure-dns.org.2
NSns4-04.azure-dns.info.2
A198.24.10.1023600
MX0 vishay-com.mail.protection.outlook.com.1
TXT"_w5a87jwpwx7ep9fa3jt1kwkgld7y2sp"1
TXT"ibmid=bd97f6e6-e3e8-48ea-97fa-a095462dcd5f"1
TXT"google-site-verification=Hmixw_zq2uOkYj__1XSqYMeC1H5HmmyJ9WCH4Ao3ISM"1
TXT"v=spf1 ip4:193.228.122.60 ip4:193.228.122.61 include:spf.protection.outlook.com include:spf2.vishay.com -all"1
TXT"d90een6jnaul0jiliihu3ujr8a"1
TXT"5eorAukxs2G9N5tnSkcXIl12IsIbJTJl08iRAuSWcGunQHgQQ+RmcIXt2Hb4eUp03WNgkjp5xbcyHsGJEYxCJQ=="1
TXT"teamviewer-sso-verification=cb2e59092a9c4e83af56c890c9e6b8a8"1
TXT"docusign=83605fdc-42b5-4042-a788-b462af2a8bab"1
TXT"apple-domain-verification=wJH4RsmRM03IcAhS"1
TXT"tva29ns8k9k550mhvt9a8pp045"1
TXT"onetrust-domain-verification=960d5d86bfd64b88a13b54cc4ba2f7e3"1
TXT"7mhbcfeiop5mukhlev3bon4oup"1
TXT"qetmamt1fnen4iu6qmgis5itu8"1

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1s), NS (2s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 2s; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35