Skip to content
https://slashfilm.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
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
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.slashfilm.com/
200https://slashfilm.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://slashfilm.com/ → https://slashfilm.com/

Consistent

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

Certificate validity

169
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, 93 ms lookup
PASS
4 A records, 93 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.227.107.69, 13.227.107.17, 13.227.107.6, 13.227.107.83
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1136.awsdns-14.org, ns-1552.awsdns-02.co.uk, ns-191.awsdns-23.com, ns-780.awsdns-33.net
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: 93 ms
Got: 93 ms
A13.227.107.69, 13.227.107.17, 13.227.107.6, 13.227.107.83
AAAA—
CNAME—
NSns-1136.awsdns-14.org, ns-1552.awsdns-02.co.uk, ns-191.awsdns-23.com, ns-780.awsdns-33.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
facebook-domain-verification=gkqvvve4h6td668bervcfnwmrsdvp3
google-site-verification=mKqJCpLxMjb8Ls939Lzz-CMCCPU5UL7QstuSWHL7DkI
pinterest-site-verification=34d367663435ac63247d9e5b02efa55e
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 93 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), 291 ms total
PASS
1 redirect(s), 291 ms total
Info::
Single redirect
Got: https://slashfilm.com → https://www.slashfilm.com/ (301)
Info::
WWW normalization redirect

https://slashfilm.com

84 ms · HTTP/1.1

301

https://www.slashfilm.com/

207 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://slashfilm.com30184 msHTTP/1.1nginx/1.18.0 (Ubuntu)
2https://www.slashfilm.com/200207 msHTTP/1.1nginx/1.18.0 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 148 URLs
PASS
robots.txt present, sitemap with 148 URLs
Info::
robots.txt is present
Got: 283 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 148 entries
Info::
Sitemap index with 148 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 283 B Sitemaps referenced 2 User-agents *, Googlebot Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /*?*ajax=
Disallow: /*/s/*
Disallow: /*/sl/*
Disallow: /search/

User-agent: Googlebot
Disallow: /sponsored/

Sitemap: https://www.slashfilm.com/sitemap_index.xml
Sitemap: https://www.slashfilm.com/?getfeed=google
sitemap.xml 200 OK
Type Sitemap Index URLs 148 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
slashfilm.com — via GoDaddy.com, LLC, 21 years old, hosted on AWS
PASS
slashfilm.com — via GoDaddy.com, LLC, 21 years old, hosted on AWS
Info::
Domain registered until Jul 26, 2026 (3 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: AS16509
Domain expiry

41 days

July 26, 2026

SSL certificate

169 days

Issued by Amazon

Domain age

21 years

Registered July 26, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.227.107.69

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created July 26, 2005 (21 years ago)
Expires July 26, 2026 (3 months)
Last Updated December 9, 2024
Name Servers ns-1136.awsdns-14.org, ns-1552.awsdns-02.co.uk, ns-191.awsdns-23.com, ns-780.awsdns-33.net
DNSSEC Not enabled
Hosting
IP Address 13.227.107.69
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.7s)

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 271 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
89 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
271 ms
Total Time Total request time from DNS lookup through full response.
271 ms

Connection waterfall

DNS Lookup 89 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 176 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU3-P11)
Got: x-amz-cf-id: FrZ71ske2KCTlGahq0kBt3WYnn2bpowxZSmSyN-4fjbc0lDp8HrIVA==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: FrZ71ske2KCTlGahq0kBt3WYnn2bpowxZSmSyN-4fjbc0lDp8HrIVA==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback