Infrastructure - https://zippyshare.com BeaverCheck Audit

D

URL Variants

Action

www/non-www, trailing slash, HTTP→HTTPS

FIX

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP version does not redirect to HTTPS

Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.zippyshare.com/

200https://zippyshare.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://zippyshare.com/

HTTP version does not redirect to HTTPS

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B

DNS Records

1 A records, 205 ms lookup

REVIEW

1 A records, 205 ms lookup

Resolves to 1 IPv4 address(es)

Got: 51.68.44.159

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: dns2.home.pl, dns3.home.pl, dns.home.pl

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (205 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 205 ms

A	51.68.44.159
AAAA	—
CNAME	—
NS	dns2.home.pl, dns3.home.pl, dns.home.pl
MX	10 mail.zippyshare.com
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 205 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

No IPv6 (AAAA) records found

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

No IPv6 Support

About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C

Crawlability

Action

robots.txt present, sitemap with 0 URLs

REVIEW

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 35 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 35 B Sitemaps referenced 0 User-agents ia_archiver Blocking No — crawling allowed

User-agent: ia_archiver
Disallow: /

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

B

HTTP Probe Timing

Total 850 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

181 ms

TCP Connect

166 ms

TLS Handshake

336 ms

Time to First Byte

850 ms

Total Time

850 ms

Connection waterfall

DNS Lookup 181 ms TCP Connect 166 ms TLS Handshake 336 ms Server Processing 167 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

53 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

53

days left

0d 30d 60d 90d+

Recommended actions

Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
Submit your domain to hstspreload.org to be added to the Chrome preload list
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+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://zippyshare.com

https://zippyshare.com

863 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://zippyshare.com	200	863 ms	HTTP/1.1	nginx/1.24.0 (Ubuntu)

A+

Domain Intelligence

zippyshare.com — via Key-Systems GmbH, 19 years, 10 months old, hosted on OVH

PASS

zippyshare.com — via Key-Systems GmbH, 19 years, 10 months old, hosted on OVH

Domain registered until Sep 6, 2026 (4 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: Key-Systems GmbH

Registrar lock is NOT enabled

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.

Hosting: OVH

Got: AS16276

Domain expiry

20 days

September 6, 2026

SSL certificate

53 days

Issued by Let's Encrypt

Domain age

19 years, 10 months

Registered September 6, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.68.44.159

Registrar

Key-Systems GmbH

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Key-Systems GmbH

Created September 6, 2006 (19 years, 10 months ago)

Expires September 6, 2026 (4 months)

Last Updated December 2, 2025

Name Servers dns.home.pl, dns2.home.pl, dns3.home.pl

DNSSEC Not enabled

Hosting

IP Address 51.68.44.159

ASN AS16276 (OVH, FR)

Provider OVH

Data source: rdap (0.9s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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