Skip to content
https://systeme.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
6 PASS 3 REVIEW
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 13 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 13 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
184 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

184
days left
0d 30d 60d 90d+

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 Records
4 A records, 48 ms lookup
PASS
4 A records, 48 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.202.52, 65.8.202.80, 65.8.202.99, 65.8.202.27
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1681.awsdns-18.co.uk, ns-1518.awsdns-61.org, ns-609.awsdns-12.net, ns-109.awsdns-13.com
Info::
5 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: 48 ms
Got: 48 ms
A65.8.202.52, 65.8.202.80, 65.8.202.99, 65.8.202.27
AAAA
CNAME
NSns-1681.awsdns-18.co.uk, ns-1518.awsdns-61.org, ns-609.awsdns-12.net, ns-109.awsdns-13.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com ip4:185.236.142.108 ip4:185.236.142.117 ~all
CAALookup not available with standard resolver
Resolved in 48 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
Redirect Chain
1 redirect(s), 181 ms total
PASS
1 redirect(s), 181 ms total
Info::
Single redirect
Got: https://systeme.io → https://systeme.io/home (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://systeme.io

https://systeme.io

79 ms · HTTP/1.1

302

https://systeme.io/home

101 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://systeme.io30279 msHTTP/1.1nginx
2https://systeme.io/home200101 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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.systeme.io/
200https://systeme.io/

Preferred variant: non-www

HTTP → HTTPS

301http://systeme.io/ https://systeme.io/

Consistent

A+
Domain Intelligence
systeme.io — via NameCheap, Inc., 10 years, 11 months old, hosted on AWS
PASS
systeme.io — via NameCheap, Inc., 10 years, 11 months old, hosted on AWS
Info::
Domain registered until Jul 6, 2028 (2 years, 2 months remaining)
Info::
Registrar: NameCheap, Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

725 days

July 6, 2028

SSL certificate

184 days

Issued by Amazon

Domain age

10 years, 11 months

Registered July 6, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.52

Registrar

NameCheap, Inc.

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar NameCheap, Inc.
Created July 6, 2015 (10 years, 11 months ago)
Expires July 6, 2028 (2 years, 2 months)
Last Updated June 8, 2024
Name Servers ns-109.awsdns-13.com, ns-1518.awsdns-61.org, ns-609.awsdns-12.net, ns-1681.awsdns-18.co.uk
Registrant Privacy service provided by Withheld for Privacy ehf
Hosting
IP Address 65.8.202.52
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (5.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 45 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 74 ms Content Transfer 0 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P6)
Got: x-amz-cf-id: 3TjM7qB_g1Kpr1KWRSBsgEyNbE8644T7ZRRX9wCQpJPuJ1kXajOfRQ==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: 3TjM7qB_g1Kpr1KWRSBsgEyNbE8644T7ZRRX9wCQpJPuJ1kXajOfRQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback