Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 932 ms totalREVIEW
https://winzip.com
297 ms · HTTP/1.1
https://www.winzip.com/
628 ms · HTTP/1.1
https://www.winzip.com/en/
7 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://winzip.com | 301 | 297 ms | HTTP/1.1 | Apache |
| 2 | https://www.winzip.com/ | 302 | 628 ms | HTTP/1.1 | Apache |
| 3 | https://www.winzip.com/en/ | 200 | 7 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
BTLS Certificate Expiry & Recommendations200 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records4 A records, 29 ms lookupPASS
| A | 98.95.119.233, 3.218.19.199, 54.175.14.92, 23.23.248.163 |
| AAAA | 2600:1f18:46:8a0:2051:9673:bd4f:926b, 2600:1f18:46:8a8:f301:b977:f3be:e02d, 2600:1f18:46:807:e81:e97d:b288:b652, 2600:1f18:46:839:7cf9:898d:647f:fc5f |
| CNAME | — |
| NS | ns-1074.awsdns-06.org, ns-754.awsdns-30.net, ns-1947.awsdns-51.co.uk, ns-371.awsdns-46.com |
| MX | 0 winzip-com.mail.protection.outlook.com |
| TXT | parallels-domain-verification=d629b252ded247b5b1ff119f86ba7abaff924883d6b6406293... atlassian-domain-verification=C5157X6GoWSIfjZLoHdhdgDjDsleN2aAUJs2Tp/C04DwfaHbW3... adobe-idp-site-verification=db79780eea47bbff0127ee18aaabe3f16aa5267b3ebd618ed764... google-site-verification=SO0-yOzBIRRdvEehzyuKf07pbNMmFwH-7pXqBo8tQ5o google-site-verification=xJEwwknKFM21CfmyWIotO5ruFjd0jmQe-tQCDz_J7m0 SPF v=spf1 include:spf.winzip.com include:spf.protection.outlook.com include:spf.dyn... google-site-verification=T0XSTuyotv3PVF3hEqx-tmAg11G6i0OVGVzufMVL19Y google-site-verification=DUVr4XGGbiaIsiR2s0UBFj3IFKgN0FekWXrqlajo3FQ google-site-verification=EttOOiGfI8Qr-6jGEEdvRexN93vbWUWvYVW-RhQ3WYs google-site-verification=39WCmb8wMb4r-OTf9ddohFBuzMkGivRJBbBtKpqyAOQ MS=ms75859401 apple-domain-verification=PMY8iOrNgNCLwkmM docusign=6b3dd13f-8a0d-4ca0-84c1-5ba512894627 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+IPv6 ReadinessIPv6 reachable (95 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 629 URLsPASS
User-Agent: *
Disallow: /cgi-bin/
Disallow: /mac/de/
Disallow: /win/*/updates/
Disallow: /include/
Disallow: /updates/
User-agent: SEOkicks
Disallow: /
User-agent: Mauibot
Disallow: /
User-agent: ZumBot
Disallow: /
Sitemap: https://www.winzip.com/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencewinzip.com — via MarkMonitor Inc., 31 years, 11 months oldPASS
106 days
October 31, 2026
200 days
Issued by Amazon
31 years, 11 months
Registered November 1, 1994
Not enabled
Protects against DNS spoofing
Unknown
2600:1f18:46:807:e81:e97d:b288:b652
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice