Infrastructure - https://power-stars-777.com BeaverCheck Audit

B

TLS Certificate Expiry & Recommendations

60 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

60

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

PASS

2 A records, 57 ms lookup

Resolves to 2 IPv4 address(es)

Got: 172.67.141.248, 104.21.94.246

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:3037::ac43:8df8, 2606:4700:3035::6815:5ef6

2 nameserver(s) configured

Got: tina.ns.cloudflare.com, jonah.ns.cloudflare.com

No MX records — email not configured via DNS

CAA records not checked

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

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 57 ms

Got: 57 ms

A	172.67.141.248, 104.21.94.246
AAAA	2606:4700:3037::ac43:8df8, 2606:4700:3035::6815:5ef6
CNAME	—
NS	tina.ns.cloudflare.com, jonah.ns.cloudflare.com
MX	—
TXT	google-site-verification=YbgzR4143opeUTNLb74K3rvVNXJBdmohd5c2x0YU2kY
CAA	Lookup not available with standard resolver

Resolved in 57 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://power-stars-777.com

https://power-stars-777.com

660 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://power-stars-777.com	200	660 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700:3037::ac43:8df8, 2606:4700:3035::6815:5ef6

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700:3037::ac43:8df8, 2606:4700:3035::6815:5ef6 Connection Reachable (17 ms)

A+

Crawlability

robots.txt present, sitemap with 21 URLs

PASS

robots.txt present, sitemap with 21 URLs

robots.txt is present

Got: 542 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 21 entries

Sitemap index with 21 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *

Disallow: /cgi-bin

Disallow: /wp-admin

Disallow: /wp-includes

Disallow: /wp-content/plugins

Disallow: /wp-content/cache

Disallow: /wp-content/themes

Disallow: /wp-trackback

Disallow: /wp-feed

Disallow: /wp-comments

Disallow: */trackback

Disallow: */feed

Disallow: */comments

Disallow: /goto/*

Disallow: /out/*

Disallow: */page/*

Disallow: /*utm*

Disallow: /?attachment_id*

Disallow: */?*


Disallow: /content_manager

Host:       https://power-stars-777.com
Sitemap:    https://power-stars-777.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 21 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.power-stars-777.com/

200https://power-stars-777.com/

Preferred variant: non-www

HTTP → HTTPS

301http://power-stars-777.com/ → https://power-stars-777.com/

Consistent

A

Domain Intelligence

power-stars-777.com — via NameCheap, Inc., 9 years, 11 months old

PASS

power-stars-777.com — via NameCheap, Inc., 9 years, 11 months old

Domain expires in 58 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Jun 20, 2026

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: NameCheap, 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.

Domain expiry

EXPIRED

June 20, 2026

SSL certificate

60 days

Issued by Google Trust Services

Domain age

9 years, 11 months

Registered June 20, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::6815:5ef6

Registrar

NameCheap, Inc.

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar NameCheap, Inc.

Created June 20, 2016 (9 years, 11 months ago)

Expires June 20, 2026 (1 months)

Last Updated June 3, 2025

Name Servers jonah.ns.cloudflare.com, tina.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2606:4700:3035::6815:5ef6

Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

PASS

DNS Lookup

48 ms

TCP Connect

17 ms

TLS Handshake

22 ms

Time to First Byte

669 ms

Total Time

673 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 583 ms Content Transfer 4 ms

A

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: 9f082a2f7e1fc653-CDG

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f082a2f7e1fc653-CDG