Skip to content
https://s-sols.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.s-sols.com/
200https://s-sols.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://s-sols.com/ https://s-sols.com/

Consistent

C
TLS Certificate Expiry & Recommendations
Action
26 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

26
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 26 days remaining
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
1 A records, 44 ms lookup
PASS
1 A records, 44 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 38.242.201.253
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: elaine.ns.cloudflare.com, clayton.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 44 ms
Got: 44 ms
A38.242.201.253
AAAA
CNAME
NSelaine.ns.cloudflare.com, clayton.ns.cloudflare.com
MX
10 mail.s-sols.com
TXT
amazonses:yWUpLWHPVHo/Mgp13o+PL8ahT8v3l+3UDc8++5+JjS4=
SPF v=spf1 a mx include:spf.sendinblue.com include:_spf.mailersend.net -all
google-site-verification=kgVdcns1DrJwPwLU41KSHev_10SLRK2auWioL9h-Gnw
CAALookup not available with standard resolver
Resolved in 44 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.

A
Redirect Chain
1 redirect(s), 232 ms total
PASS
1 redirect(s), 232 ms total
Info::
Single redirect
Got: https://s-sols.com → https://www.s-sols.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://s-sols.com

https://s-sols.com

80 ms · HTTP/1.1

302

https://www.s-sols.com/

153 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://s-sols.com30280 msHTTP/1.1nginx
2https://www.s-sols.com/200153 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 1889 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1889 B Sitemaps referenced 6 User-agents *, GoogleBot, Yandex Blocking No — crawling allowed
User-agent: *
Disallow: /data/accelerator-preview/*
Disallow: /cgi-bin
Disallow: /?
Disallow: /wp-
Disallow: /wp/
Disallow: *?s=
Disallow: *&s=
Disallow: /search/
Disallow: /users/
Disallow: */trackback
Allow: */feed
Allow: */rss
Disallow: */embed
Disallow: */wlwmanifest.xml
Disallow: /xmlrpc.php
Disallow: *utm=
Disallow: *openstat=
Allow: */uploads

User-agent: GoogleBot
Disallow: /data/accelerator-preview/*
Disallow: /cgi-bin
Disallow: /?
Disallow: /wp-
Disallow: /wp/
Disallow: *?s=
Disallow: *&s=
Disallow: /search/
Disallow: /users/
Disallow: */trackback
Disallow: */rss
Disallow: */embed
Disallow: */wlwmanifest.xml
Disallow: /xmlrpc.php
Disallow: *utm=
Disallow: *openstat=
Allow: */uploads
Allow: /*/*.js
Allow: /*/*.css
Allow: /wp-*.png
Allow: /wp-*.jpg
Allow: /wp-*.jpeg
Allow: /wp-*.gif
Allow: /wp-admin/admin-ajax.php

User-agent: Yandex
Disallow: /data/accelerator-preview/*
Disallow: /cgi-bin
Disallow: /?
Disallow: /wp-
Disallow: /wp/
Disallow: *?s=
Disallow: *&s=
Disallow: /search/
Disallow: /users/
Disallow: */trackback
Disallow: */rss
Disallow: */embed
Disallow: */wlwmanifest.xml
Disallow: /xmlrpc.php
Allow: */uploads
Allow: /*/*.js
Allow: /*/*.css
Allow: /wp-*.png
Allow: /wp-*.jpg
Allow: /wp-*.jpeg
Allow: /wp-*.gif
Allow: /feed/turbo/
Allow: /feed/zen/
Allow: /wp-admin/admin-ajax.php
Clean-param: utm_source&utm_medium&utm_campaign 
Clean-param: openstat
Clean-param: wmc-currency
Clean-param: etext
Clean-param: aid
Clean-param: rdt_cid

Sitemap: https://www.s-sols.com/sitemap_index.xml
Sitemap: https://www.s-sols.com/post-sitemap.xml
Sitemap: https://www.s-sols.com/page-sitemap.xml
Sitemap: https://www.s-sols.com/product-sitemap.xml
Sitemap: https://www.s-sols.com/doc-sitemap.xml
Sitemap: https://www.s-sols.com/news-sitemap.xml

Host: https://www.s-sols.com

Allow: /products/wordpress/post-docx-source/
Allow: /ru/products/wordpress/post-docx-source/
A+
Domain Intelligence
s-sols.com — via Cloudflare, Inc., 9 years, 9 months old, hosted on CONTABO, DE
PASS
s-sols.com — via Cloudflare, Inc., 9 years, 9 months old, hosted on CONTABO, DE
Info::
Domain registered until Sep 6, 2026 (4 months remaining)
Info::
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.
Info::
Registrar: Cloudflare, Inc.
Warning::
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.
Info::
Hosting: CONTABO, DE
Got: AS51167
Domain expiry

85 days

September 6, 2026

SSL certificate

26 days

Issued by ZeroSSL

Domain age

9 years, 9 months

Registered September 6, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CONTABO, DE

ASN AS51167

38.242.201.253

Registrar

Cloudflare, Inc.

Unlocked 2 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
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created September 6, 2016 (9 years, 9 months ago)
Expires September 6, 2026 (4 months)
Last Updated August 7, 2025
Name Servers clayton.ns.cloudflare.com, elaine.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 38.242.201.253
ASN AS51167 (CONTABO, DE)
Provider CONTABO, DE
Data source: rdap (0.3s)

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

A+
HTTP Probe Timing
Total 134 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
28 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
134 ms
Total Time Total request time from DNS lookup through full response.
135 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 28 ms TLS Handshake 31 ms Server Processing 28 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.

Send Feedback