Infrastructure - https://lovetoknow.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

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

Both www and non-www versions serve content

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

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.lovetoknow.com/

200https://lovetoknow.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

TLS Certificate Expiry & Recommendations

54 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

54

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

1 A records, 34 ms lookup

PASS

1 A records, 34 ms lookup

Resolves to 1 IPv4 address(es)

Got: 54.242.49.189

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1471.awsdns-55.org, ns-1576.awsdns-05.co.uk, ns-461.awsdns-57.com, ns-707.awsdns-24.net

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: 34 ms

Got: 34 ms

A	54.242.49.189
AAAA	—
CNAME	—
NS	ns-1471.awsdns-55.org, ns-1576.awsdns-05.co.uk, ns-461.awsdns-57.com, ns-707.awsdns-24.net
MX	10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com
TXT	google-site-verification=RaEy9i1n_58zWyDMT8Sbp0qEEdh_YqwwKTVmBAxLmSo 'lovetoknow.com:v=spf1(mx(-all:604800 amazonses:4cb3HuThVdzOiCEDZ0eiHH1yz2eRemPYGoWTv8VFeOs= google-site-verification=5TwHh9TQ7jCeju8X8Vttf4sPEuIKd627OHcAW1gWU google-site-verification=C2U47sYJ9LlAVsAqMMIBUEjWc9rCrbVOA1_LaYA-kmk google-site-verification=HFVd6DgB_Kte5rLgODQmJzYYgw7jqpbGdAtWPpuoxU0 google-site-verification=NliMl-jybnA8v8-X1TzCEi413762Dx0mnmT7hnu0I58 google-site-verification=WXdlIcQyN1HdY9yAQ-L18AarbpytgPotTmF3ujMKRaY google-site-verification=_ALlv43wGDs2My-mGARNomLNG1F0CqwymPD6yECK-NY google-site-verification=_GVQNd9yXH2A5Xzo1SginWu4zc8KeHO_oOwMrFR_8M4 google-site-verification=iwGYeHPQkxPG5hcVG3ETEHEYOb3M091ftaPctw8wp48 google-site-verification=jP1FKfVP6qUJ26ivbpFotbc6iuPFqpWvaSlBqoQgrOk google-site-verification=nc4HRPZ1hmdb7iXtuBDaHLF5HPtCuodnLf_LAo_ll0k google-site-verification=vXCrBFk5InC8W6VsQmft3rZh8jMuuzuoWMtZUrS1dOM SPF v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
CAA	Lookup not available with standard resolver

Resolved in 34 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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), 373 ms total

PASS

1 redirect(s), 373 ms total

Single redirect

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

WWW normalization redirect

https://lovetoknow.com

304 ms · HTTP/1.1

301

https://www.lovetoknow.com/

69 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://lovetoknow.com	301	304 ms	HTTP/1.1	Apache/2.4.51 () OpenSSL/1.0.2k-fips PHP/8.2.19
2	https://www.lovetoknow.com/	200	69 ms	HTTP/1.1	Apache

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 10 URLs

PASS

robots.txt present, sitemap with 10 URLs

robots.txt is present

Got: 640 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 10 entries

Sitemap index with 10 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 640 B Sitemaps referenced 1 User-agents *, Mediapartners-Google Blocking No — crawling allowed


User-agent: *
Disallow: /1004147*
Disallow: /frontend.
Disallow: /frontend_
Disallow: /backend.
Disallow: /backend_
Disallow: /css/
Disallow: /js/
Disallow: /sf/
Disallow: /print/
Disallow: /search?
Disallow: /image/
Disallow: /advice$
Disallow: /advice/
Disallow: /botCheck.json


User-agent: Mediapartners-Google
Disallow: /index.
Disallow: /wiki/index.
Disallow: /frontend.
Disallow: /frontend_
Disallow: /backend.
Disallow: /backend_
Disallow: /css/
Disallow: /js/
Disallow: /sf/
Disallow: /print/
Disallow: /search?
Disallow: /advice$
Disallow: /advice/
Disallow: /botCheck.json

Sitemap: https://www.lovetoknow.com/sitemap-index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 10 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

lovetoknow.com — via Network Solutions, LLC, 22 years, 11 months old, hosted on AWS

PASS

lovetoknow.com — via Network Solutions, LLC, 22 years, 11 months old, hosted on AWS

Domain registered until Sep 11, 2029 (3 years, 5 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: Network Solutions, LLC

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: AWS

Got: AS14618

Domain expiry

1184 days

September 11, 2029

SSL certificate

54 days

Issued by Let's Encrypt

Domain age

22 years, 11 months

Registered September 11, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.242.49.189

Registrar

Network Solutions, 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 Network Solutions, LLC

Created September 11, 2003 (22 years, 11 months ago)

Expires September 11, 2029 (3 years, 5 months)

Last Updated July 13, 2024

Name Servers ns-1471.awsdns-55.org, ns-1576.awsdns-05.co.uk, ns-461.awsdns-57.com, ns-707.awsdns-24.net

DNSSEC Not enabled

Hosting

IP Address 54.242.49.189

ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.1s)

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

PASS

DNS Lookup

16 ms

TCP Connect

67 ms

TLS Handshake

138 ms

Time to First Byte

289 ms

Total Time

290 ms

Connection waterfall

DNS Lookup 16 ms TCP Connect 67 ms TLS Handshake 138 ms Server Processing 68 ms Content Transfer 0 ms