Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

301 Moved Permanently

Checks

4 PASS 4 REVIEW 1 FIX

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.

Redirect Chain

1 redirect(s), 1113 ms total

REVIEW

1 redirect(s), 1113 ms total

Single redirect

Got: https://4shared.com → https://www.4shared.com (301)

WWW normalization redirect

Redirect overhead: 1113 ms total

Got: 1113 ms

https://4shared.com

520 ms · HTTP/1.1

301

https://www.4shared.com

593 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://4shared.com	301	520 ms	HTTP/1.1	nginx
2	https://www.4shared.com	200	593 ms	HTTP/1.1	571

See the visual redirect chain in the HTTP Probe tab →

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

URL Variants

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

REVIEW

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 correctly 301-redirects to HTTPS

www / non-www

200https://www.4shared.com/

200https://4shared.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://4shared.com/ → https://www.4shared.com

Consistent

TLS Certificate Expiry & Recommendations

85 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

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
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 Records

4 A records, 33 ms lookup

PASS

4 A records, 33 ms lookup

Resolves to 4 IPv4 address(es)

Got: 204.155.146.95, 204.155.149.41, 204.155.149.43, 204.155.149.42

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns7.4shared.com, ns5.4shared.com, ns6.4shared.com

2 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.

SPF record present in TXT

DNS resolution time: 33 ms

Got: 33 ms

A	204.155.146.95, 204.155.149.41, 204.155.149.43, 204.155.149.42
AAAA	—
CNAME	—
NS	ns7.4shared.com, ns5.4shared.com, ns6.4shared.com
MX	0 mx.4shared.com 100 mail2.4shared.com
TXT	google-site-verification=wnshsdUOq87bB3o71D2qFoozrfJpFstOhnMoBkwKvQ0 google-site-verification=Mw9gzWphXfWBl5T2CY-aYDOnJIleNTR-WO7zNnJs54w SPF v=spf1 include:_spf.4shared.com include:_spf.google.com -all
CAA	Lookup not available with standard resolver

Resolved in 33 ms

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.

A+

Crawlability

robots.txt present, sitemap with 4910 URLs

PASS

robots.txt present, sitemap with 4910 URLs

robots.txt is present

Got: 79 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 4910 entries

Sitemap index with 4910 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 79 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /rest/
Sitemap: https://www.4shared.com/web/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 4910 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

4shared.com — via URL Solutions, Inc., 21 years, 7 months old, hosted on WZ-US-40824 - Webzilla Inc., US

PASS

4shared.com — via URL Solutions, Inc., 21 years, 7 months old, hosted on WZ-US-40824 - Webzilla Inc., US

Domain registered until Jan 11, 2027 (8 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: URL Solutions, Inc.

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: WZ-US-40824 - Webzilla Inc., US

Got: AS40824

Domain expiry

209 days

January 11, 2027

SSL certificate

85 days

Issued by GoDaddy.com, Inc.

Domain age

21 years, 7 months

Registered January 11, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WZ-US-40824 - Webzilla Inc., US

ASN AS40824

204.155.149.41

Registrar

URL Solutions, Inc.

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar URL Solutions, Inc.

Created January 11, 2005 (21 years, 7 months ago)

Expires January 11, 2027 (8 months)

Last Updated December 3, 2024

Name Servers ns5.4shared.com, ns6.4shared.com, ns7.4shared.com

DNSSEC Not enabled

Hosting

IP Address 204.155.149.41

ASN AS40824 (WZ-US-40824 - Webzilla Inc., US)

Provider WZ-US-40824 - Webzilla Inc., US

Data source: rdap (0.4s)

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

HTTP Probe Timing

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

PASS

DNS Lookup

36 ms

TCP Connect

129 ms

TLS Handshake

261 ms

Time to First Byte

555 ms

Total Time

555 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 129 ms TLS Handshake 261 ms Server Processing 129 ms Content Transfer 0 ms

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.