Skip to content
https://slides.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
170 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

170
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
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 32.194.18.231, 52.22.148.247
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1322.awsdns-37.org, ns-183.awsdns-22.com, ns-1896.awsdns-45.co.uk, ns-944.awsdns-54.net
Info::
7 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: 9 ms
Got: 9 ms
A32.194.18.231, 52.22.148.247
AAAA
CNAME
NSns-1322.awsdns-37.org, ns-183.awsdns-22.com, ns-1896.awsdns-45.co.uk, ns-944.awsdns-54.net
MX
1 aspmx.l.google.com
3 alt2.aspmx.l.google.com
3 alt1.aspmx.l.google.com
5 aspmx2.googlemail.com
5 aspmx4.googlemail.com
5 aspmx3.googlemail.com
5 aspmx5.googlemail.com
TXT
google-site-verification=YfMESTlL7SyDvG0C9wrSlVbTgX9k98LQqj0UvvliCB8
SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:smtp1.uservoi...
CAALookup not available with standard resolver
Resolved in 9 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://slides.com

https://slides.com

483 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://slides.com200483 msHTTP/1.1nginx/1.18.0 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 259 URLs
PASS
robots.txt present, sitemap with 259 URLs
Info::
robots.txt is present
Got: 204 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 259 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 204 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# To ban all spiders from the entire site uncomment the next two lines:
# User-Agent: *
# Disallow: /

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

302https://www.slides.com/
200https://slides.com/

Preferred variant: non-www

HTTP → HTTPS

301http://slides.com/ https://slides.com:443/

Consistent

A+
Domain Intelligence
slides.com — via GoDaddy.com, LLC, 31 years, 9 months old, hosted on AWS
PASS
slides.com — via GoDaddy.com, LLC, 31 years, 9 months old, hosted on AWS
Info::
Domain registered until Dec 21, 2028 (2 years, 8 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: GoDaddy.com, LLC
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: AWS
Got: AS14618
Domain expiry

888 days

December 21, 2028

SSL certificate

170 days

Issued by Amazon

Domain age

31 years, 9 months

Registered December 22, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

32.194.18.231

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created December 22, 1994 (31 years, 9 months ago)
Expires December 21, 2028 (2 years, 8 months)
Last Updated November 29, 2022
Name Servers ns-1322.awsdns-37.org, ns-183.awsdns-22.com, ns-1896.awsdns-45.co.uk, ns-944.awsdns-54.net
DNSSEC Not enabled
Hosting
IP Address 32.194.18.231
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
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 490 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
93 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
189 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
489 ms
Total Time Total request time from DNS lookup through full response.
491 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 93 ms TLS Handshake 189 ms Server Processing 200 ms Content Transfer 2 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback