Skip to content
https://wpguardian.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a06:98c1:3120::, 2a06:98c1:3121::
Info::
IPv6 connection error
Got: dial tcp6 [2a06:98c1:3120::]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2a06:98c1:3120::, 2a06:98c1:3121:: Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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

Certificate validity

54
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 15 ms lookup
PASS
2 A records, 15 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.0, 188.114.97.0
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3120::, 2a06:98c1:3121::
Info::
2 nameserver(s) configured
Got: gene.ns.cloudflare.com, jeff.ns.cloudflare.com
Info::
1 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: 15 ms
Got: 15 ms
A188.114.96.0, 188.114.97.0
AAAA2a06:98c1:3120::, 2a06:98c1:3121::
CNAME—
NSgene.ns.cloudflare.com, jeff.ns.cloudflare.com
MX
0 wpguardian-com.mail.protection.outlook.com
TXT
MS=ms30190123
google-site-verification=Z47dTVHWFPOBBfCvmNnoUtNntm2y9sqLyVFosuxXayE
SPF v=spf1 include:spf.protection.outlook.com include:1784136.spf01.hubspotemail.net...
CAALookup not available with standard resolver
Resolved in 15 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://wpguardian.com

https://wpguardian.com

516 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wpguardian.com200516 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 172 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 172 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://wpguardian.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.wpguardian.com/
200https://wpguardian.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
wpguardian.com — via GoDaddy.com, LLC, 12 years, 3 months old
PASS
wpguardian.com — via GoDaddy.com, LLC, 12 years, 3 months old
Info::
Domain registered until Mar 4, 2027 (10 months remaining)
Info::
DNSSEC is enabled
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.
Domain expiry

262 days

March 4, 2027

SSL certificate

54 days

Issued by Google Trust Services

Domain age

12 years, 3 months

Registered March 4, 2014

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3120::

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created March 4, 2014 (12 years, 3 months ago)
Expires March 4, 2027 (10 months)
Last Updated February 18, 2026
Name Servers gene.ns.cloudflare.com, jeff.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2a06:98c1:3120::
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 12 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 252 ms Content Transfer 2 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9f07300f7b7e97ad-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f07300f7b7e97ad-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback