Skip to content
https://plerdy.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.14.92: lookup 104.26.14.92: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.15.92: lookup 104.26.15.92: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.73.224: lookup 172.67.73.224: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::ac43:49e0: lookup 2606:4700:20::ac43:49e0: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:f5c: lookup 2606:4700:20::681a:f5c: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:e5c: lookup 2606:4700:20::681a:e5c: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.plerdy.com/
200https://plerdy.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
3 A records, 36 ms lookup
PASS
3 A records, 36 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.14.92, 104.26.15.92, 172.67.73.224
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:49e0, 2606:4700:20::681a:f5c, 2606:4700:20::681a:e5c
Info::
2 nameserver(s) configured
Got: fiona.ns.cloudflare.com, nitin.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A104.26.14.92, 104.26.15.92, 172.67.73.224
AAAA2606:4700:20::ac43:49e0, 2606:4700:20::681a:f5c, 2606:4700:20::681a:e5c
CNAME—
NSfiona.ns.cloudflare.com, nitin.ns.cloudflare.com
MX
18 isaac.mx.cloudflare.net
45 amir.mx.cloudflare.net
69 linda.mx.cloudflare.net
TXT
ahrefs-site-verification_5ccd369075fd72f75ee1ac15a644f972cd45afb10f8ea55e7dd42d4...
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
google-site-verification=XqBv8padlJ7PVreaBTGI1mEPqcwQIMxAJVIYQ0BA3Ok
ca3-38e78365b16d4615bd2bf5a754bd44d2
CAALookup not available with standard resolver
Resolved in 36 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 35ms across 3 resolvers (spread 31ms)
PASS
Mean 35ms across 3 resolvers (spread 31ms)
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 38ms
Got: 38ms via 8.8.8.8:53
Info::
Quad9: 49ms
Got: 49ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 536 ms total
PASS
1 redirect(s), 536 ms total
Info::
Single redirect
Got: https://plerdy.com → https://www.plerdy.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 536 ms total
Got: 536 ms

https://plerdy.com

229 ms · HTTP/1.1

301

https://www.plerdy.com/

307 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://plerdy.com301229 msHTTP/1.1cloudflare
2https://www.plerdy.com/200307 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:49e0, 2606:4700:20::681a:f5c, 2606:4700:20::681a:e5c
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:49e0, 2606:4700:20::681a:f5c, 2606:4700:20::681a:e5c Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 1000 URLs
PASS
robots.txt present, sitemap with 1000 URLs
Info::
robots.txt is present
Got: 692 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1000 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 692 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Disallow: /*wc-ajax*

Disallow: *?filter_*

Disallow: *?product_cat=*

Disallow: */wp-json/*

Disallow: */feed/

Disallow: *.html

Disallow: */tag/*

Disallow: *.pdf

Disallow: *Ajax*

Disallow: /*/product/*

Disallow: /*/features/page/*/

Disallow: /*/plerdyTheme/*

Disallow: /*/neeesw/

Disallow: /ru/page/*

Disallow: /ua/page/*

Disallow: /es/page/*

Disallow: /fr/page/*

Disallow: /pt/page/*

Disallow: /pl/page/*

Disallow: /page/*

# Sitemap

Sitemap: https://www.plerdy.com/post-sitemap.xml

Sitemap: https://www.plerdy.com/post-sitemap2.xml

Sitemap: https://www.plerdy.com/page-sitemap.xml

Sitemap: https://www.plerdy.com/category-sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1000 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
plerdy.com — via 101domain GRS Limited, 11 years old
PASS
plerdy.com — via 101domain GRS Limited, 11 years old
Warning::
Domain expires in 45 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Oct 14, 2026
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: 101domain GRS Limited
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

45 days

October 14, 2026

SSL certificate

63 days

Issued by Google Trust Services

Domain age

11 years

Registered October 14, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:e5c

Registrar

101domain GRS Limited

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 101domain GRS Limited
Created October 14, 2015 (11 years ago)
Expires October 14, 2026 (1 months)
Last Updated October 3, 2025
Name Servers fiona.ns.cloudflare.com, nitin.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:e5c
Data source: rdap (0.2s)

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 264 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
264 ms
Total Time Total request time from DNS lookup through full response.
264 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 186 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a32d6597ef250051-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a32d6597ef250051-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback