Skip to content
https://pearltrees.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.pearltrees.com/
200https://pearltrees.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

B
Redirect Chain
2 redirect(s), 211 ms total
REVIEW
2 redirect(s), 211 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://pearltrees.com to https://www.pearltrees.com/
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: http://www.pearltrees.com/

https://pearltrees.com

73 ms · HTTP/1.1

301

http://www.pearltrees.com/

64 ms · HTTP/1.1

302

https://www.pearltrees.com/

74 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pearltrees.com30173 msHTTP/1.1Apache
2http://www.pearltrees.com/30264 msHTTP/1.1Apache
3https://www.pearltrees.com/20074 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://pearltrees.com to https://www.pearltrees.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

88
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
1 A records, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 46.105.32.253
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns-2-a.gandi.net, ns-137-c.gandi.net, ns-1-b.gandi.net
Info::
2 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: 31 ms
Got: 31 ms
A46.105.32.253
AAAA—
CNAME—
NSns-2-a.gandi.net, ns-137-c.gandi.net, ns-1-b.gandi.net
MX
10 mx1.emailsrvr.com
20 mx2.emailsrvr.com
TXT
MS=ms13150879
SPF v=spf1 a ip4:163.172.33.48 include:emailsrvr.com include:_mailcust.gandi.net inc...
google-site-verification=Z4_oMbxxdrkz_UIT4Jn1yFpYQwDo6hvU4C78zk_7brE
google-site-verification=6J4ztdSJWFUiISaygfxFY4qGiNl_VK503kcsWAMCJNk
google-site-verification=GztypySVdNXT7qmhkh16u7a3uShdgZOxg_wJgZuFFQw
google-site-verification=5Trq_gWnHrhACxnyc3ID1ogknbX6Fsq1Qp7VVvKJRm4
CAALookup not available with standard resolver
Resolved in 31 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+
Crawlability
robots.txt present, sitemap with 514 URLs
PASS
robots.txt present, sitemap with 514 URLs
Info::
robots.txt is present
Got: 76 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 514 entries
Info::
Sitemap index with 514 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 76 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /s

Sitemap: https://www.pearltrees.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 514 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
pearltrees.com — via Gandi SAS, 18 years old, hosted on OVH
PASS
pearltrees.com — via Gandi SAS, 18 years old, hosted on OVH
Info::
Domain registered until Jul 24, 2026 (3 months remaining)
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: Gandi SAS
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.
Info::
Hosting: OVH
Got: AS16276
Domain expiry

12 days

July 24, 2026

SSL certificate

88 days

Issued by DigiCert Inc

Domain age

18 years

Registered July 24, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

46.105.32.253

Registrar

Gandi SAS

Unlocked 3 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 Gandi SAS
Created July 24, 2008 (18 years ago)
Expires July 24, 2026 (3 months)
Last Updated June 23, 2025
Name Servers ns-1-b.gandi.net, ns-137-c.gandi.net, ns-2-a.gandi.net
DNSSEC Not enabled
Hosting
IP Address 46.105.32.253
ASN AS16276 (OVH, FR)
Provider OVH
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 92 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
20 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
93 ms
Total Time Total request time from DNS lookup through full response.
93 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 20 ms TLS Handshake 22 ms Server Processing 29 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback