Infrastructure - https://smore.com BeaverCheck Audit

D

URL Variants

Action

www/non-www, trailing slash, HTTP→HTTPS

FIX

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.smore.com/

200https://smore.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://smore.com/ → http://www.smore.com/

HTTP version does not redirect to HTTPS

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

85 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

85

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, 46 ms lookup

PASS

2 A records, 46 ms lookup

Resolves to 2 IPv4 address(es)

Got: 141.193.213.20, 141.193.213.21

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1668.awsdns-16.co.uk, ns-1039.awsdns-01.org, ns-894.awsdns-47.net, ns-450.awsdns-56.com

5 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 46 ms

Got: 46 ms

A	141.193.213.20, 141.193.213.21
AAAA	—
CNAME	—
NS	ns-1668.awsdns-16.co.uk, ns-1039.awsdns-01.org, ns-894.awsdns-47.net, ns-450.awsdns-56.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com
TXT	SPF v=spf1 include:242953071.spf06.hubspotemail.net include:mail.zendesk.com redirec... _globalsign-domain-verification=IG4UdrI9gc_SVSE132aTagdWhxkvONdbIBhHhhcMlP stripe-verification=ddb5afcfcee77f3bc536281ac451570ded8302305803c64093fb867c5e6f... google-site-verification=IcMqPvj07F_fcLNnut8rpVg2TPGoIFDO48pFvs2E-Dk amazonses:9OOgl3cfRxloOND+Zxgb/U1u+Q0OkTwzBPSqK4Q/8vc= google-site-verification=mJr1ioXy3bYuxDSUTlshqHoE6KiSBaGNsHEVvAGcUqw
CAA	Lookup not available with standard resolver

Resolved in 46 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), 645 ms total

PASS

1 redirect(s), 645 ms total

Single redirect

Got: https://smore.com → https://www.smore.com/ (301)

WWW normalization redirect

Redirect overhead: 645 ms total

Got: 645 ms

https://smore.com

209 ms · HTTP/1.1

301

https://www.smore.com/

437 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://smore.com	301	209 ms	HTTP/1.1	cloudflare
2	https://www.smore.com/	200	437 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 9 URLs

PASS

robots.txt present, sitemap with 9 URLs

robots.txt is present

Got: 301 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 9 entries

Sitemap index with 9 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 301 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

Sitemap: https://www.smore.com/sitemap_index.xml


User-agent: *

Disallow: /wp-admin/

Disallow: /wp-includes/

Disallow: /cgi-bin/

Disallow: /wp-content/plugins/

Disallow: /wp-content/cache/

Disallow: /wp-content/themes/


# Allow access to essential admin-ajax

Allow: /wp-admin/admin-ajax.php

sitemap.xml 200 OK

Type Sitemap Index URLs 9 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

smore.com — via Amazon Registrar, Inc., 23 years, 4 months old, hosted on Cloudflare

PASS

smore.com — via Amazon Registrar, Inc., 23 years, 4 months old, hosted on Cloudflare

Domain registered until Apr 6, 2028 (1 years, 11 months remaining)

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.

Registrar: Amazon Registrar, Inc.

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.

Hosting: Cloudflare

Got: AS209242

Domain expiry

661 days

April 6, 2028

SSL certificate

85 days

Issued by Google Trust Services

Domain age

23 years, 4 months

Registered April 6, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

141.193.213.20

Registrar

Amazon Registrar, 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 Amazon Registrar, Inc.

Created April 6, 2003 (23 years, 4 months ago)

Expires April 6, 2028 (1 years, 11 months)

Last Updated December 3, 2022

Name Servers ns-1039.awsdns-01.org, ns-1668.awsdns-16.co.uk, ns-450.awsdns-56.com, ns-894.awsdns-47.net

DNSSEC Not enabled

Hosting

IP Address 141.193.213.20

ASN AS209242 (CLOUDFLARESPECTRUM Cloudflare, Inc., US)

Provider Cloudflare

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 252 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

52 ms

TCP Connect

1 ms

TLS Handshake

6 ms

Time to First Byte

253 ms

Total Time

253 ms

Connection waterfall

DNS Lookup 52 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 194 ms Content Transfer 0 ms

A

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: MAD)

Got: cf-ray: 9f08611dbaffd872-MAD

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f08611dbaffd872-MAD