Skip to content
https://strikingly.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://strikingly.com/ → https://www.strikingly.com/

Consistent

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

Certificate validity

87
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
2 A records, 35 ms lookup
PASS
2 A records, 35 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.219.112.130, 54.183.102.22
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-106.awsdns-13.com, ns-1371.awsdns-43.org, ns-692.awsdns-22.net, ns-1944.awsdns-51.co.uk
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: 35 ms
Got: 35 ms
A54.219.112.130, 54.183.102.22
AAAA—
CNAME—
NSns-106.awsdns-13.com, ns-1371.awsdns-43.org, ns-692.awsdns-22.net, ns-1944.awsdns-51.co.uk
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 alt4.aspmx.l.google.com
30 alt3.aspmx.l.google.com
TXT
google-site-verification=TKwWJfJPcPQKEnxBYXMJIj8H-w9WEtBvLzglWFEmLas
facebook-domain-verification=ecmxxlh2q3b2p9dbuytwa6yzknhdk1
openai-domain-verification=dv-8v0KWSkvFD3JoIA3BtUOj5hZ
google-site-verification=gczQ5cZD4lqKP-IsRMTNimBKQGTgAoAxf4Qeun9xddQ
SPF v=spf1 ip4:192.254.124.239 ip4:167.89.42.111 ip4:50.31.50.217 ip4:64.99.180.0/24...
MS=ms61370214
atlassian-domain-verification=GQM2BZmuFkNZ4AXSSMknjN4sVMQYoaXKei0Fp9hcWEM9J98U74...
CAALookup not available with standard resolver
Resolved in 35 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), 560 ms total
PASS
1 redirect(s), 560 ms total
Info::
Single redirect
Got: https://strikingly.com → https://www.strikingly.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 560 ms total
Got: 560 ms

https://strikingly.com

497 ms · HTTP/1.1

301

https://www.strikingly.com/

63 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://strikingly.com301497 msHTTP/1.1openresty
2https://www.strikingly.com/20063 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 57 URLs
PASS
robots.txt present, sitemap with 57 URLs
Info::
robots.txt is present
Got: 666 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 57 entries
Info::
Sitemap index with 57 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 666 B Sitemaps referenced 1 User-agents *, baiduspider, Baiduspider, adsbot-google 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: /
User-Agent: *
Disallow: /a/
Disallow: /r/
Disallow: /s/sites/
Disallow: /s/audience/
Disallow: /s/reseller/user/
Disallow: /s/analytics/
Disallow: /logo/

User-agent: baiduspider
allow:/article/blog/*.mip
User-agent: Baiduspider
allow: /article/blog/*.mip

User-agent: *
Disallow: /article/blog/*.mip
# Google adsbot ignores robots.txt unless specifically named!
User-agent: adsbot-google
Disallow: /s/screenshot/
Sitemap: https://www.strikingly.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 57 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
strikingly.com — via NameCheap, Inc., 25 years, 7 months old, hosted on AWS
PASS
strikingly.com — via NameCheap, Inc., 25 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 21, 2030 (3 years, 9 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: NameCheap, 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: AWS
Got: AS16509
Domain expiry

1282 days

January 21, 2030

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

25 years, 7 months

Registered January 21, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.219.112.130

Registrar

NameCheap, Inc.

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 NameCheap, Inc.
Created January 21, 2001 (25 years, 7 months ago)
Expires January 21, 2030 (3 years, 9 months)
Last Updated November 15, 2020
Name Servers ns-106.awsdns-13.com, ns-1371.awsdns-43.org, ns-1944.awsdns-51.co.uk, ns-692.awsdns-22.net
DNSSEC Not enabled
Hosting
IP Address 54.219.112.130
ASN AS16509 (AMAZON-02 - 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 551 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
169 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
176 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
551 ms
Total Time Total request time from DNS lookup through full response.
551 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 169 ms TLS Handshake 176 ms Server Processing 174 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