patek.com

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

Registration

info

.com generic · Gandi SAS · expires 2027-03-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Gandi SAS
Registered
7 March 1996
Last changed
5 February 2026
Expires
8 March 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited
Registry nameservers
ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.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-03-08 #3
    The registration is valid until 2027-03-08 (136 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info
NS in the zone
ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-34.azure-dns.com150.171.10.34 2603:1061:0:10::22AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US150.171.10.34 2603:1061:0:10::22
ns2-34.azure-dns.net150.171.16.34 2620:1ec:8ec:10::22AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-34.azure-dns.org13.107.222.34 2a01:111:4000:10::22AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-34.azure-dns.info13.107.206.34 2620:1ec:bda:10::22AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.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

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-34.azure-dns.com 150.171.10.34NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns1-34.azure-dns.com 2603:1061:0:10::22NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns2-34.azure-dns.net 150.171.16.34NOERROR, 7 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns2-34.azure-dns.net 2620:1ec:8ec:10::22NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3-34.azure-dns.org 13.107.222.34NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-34.azure-dns.org 2a01:111:4000:10::22NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-34.azure-dns.info 13.107.206.34NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-34.azure-dns.info 2620:1ec:bda:10::22NOERROR, 8 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2-34.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-34.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • ✓ 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

pass

serial 1 · primary ns1-34.azure-dns.com

Found

Primary (MNAME)
ns1-34.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-34.azure-dns.com (150.171.10.34)1
ns1-34.azure-dns.com (2603:1061:0:10::22)1
ns2-34.azure-dns.net (150.171.16.34)1
ns2-34.azure-dns.net (2620:1ec:8ec:10::22)1
ns3-34.azure-dns.org (13.107.222.34)1
ns3-34.azure-dns.org (2a01:111:4000:10::22)1
ns4-34.azure-dns.info (13.107.206.34)1
ns4-34.azure-dns.info (2620:1ec:bda:10::22)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-34.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

25 records at the apex

Found

Read from
150.171.10.34:53
TypeValueTTL
SOAns1-34.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-34.azure-dns.com.600
NSns2-34.azure-dns.net.600
NSns3-34.azure-dns.org.600
NSns4-34.azure-dns.info.600
A150.171.109.10060
MX10 mail20.patek.com.600
MX10 mail10.patek.com.600
TXT"4308894bebaf4d489d54887feba35968"300
TXT"amazonses:S9gLkrvavVJXHUoKzUAY1PHFsFX+7w2tiZ1RMF8fEKY="300
TXT"00DbW000004OeRp=1TBbW0000000AKL"300
TXT"gjrq8vpq15c6tj5j6zk5kln1zx7gqknj"300
TXT"e00ac89c-6d3a-4dd0-acbf-6458e9f0cffc"300
TXT"v=spf1 ip4:91.209.28.11 ip4:91.209.28.12 ip4:91.209.28.37 ip4:91.209.28.40 mx:patek.com include:_spf-sfdc.successfactors.com include:_spf.salesforce.com include:cust-spf.exacttarget.com -all"300
TXT"MS=ms84056575"300
TXT"amazonses:jGFpL2ZIeNrXpvV+1jnUtrOCq2pt3G7PsekQGfSTYIo="300
TXT"miro-verification=529267180035e7f82d592d975a0fe9965a5916a8"300
TXT"00DFS000006nRtF=1TBFS0000001M05"300
TXT"ms-domain-verification=0a39a17f-e137-4c47-95eb-bd4a8d98ae06"300
TXT"SFMC-VSL3S82lYUaB_gvmAerAfZEg4LkE46Tv_2_jW99S"300
TXT"docusign=e7f150de-7de4-4d28-a140-5484e010ac23"300
TXT"MS=ms10931518"300
TXT"Gtcq9eT9VbE4rnMujtr5Q8yQximoTxVgxi/wYE31brrekyrvHG87tIGijbUeoemjouAV1hjtdZGcwCHMCqgE8A=="300
TXT"google-site-verification=bnyrm8lcRu7N6GguP2jkHfxquspyT-Ecj1a9YpW2VyU"300
TXT"00D68000002755q=1TBTG00000001Ab"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; 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