Skip to content
https://profittolife.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 187.77.18.224 does not match any cert SAN: srv1363566.hstgr.cloud
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a02:4780:4:dab7::1 does not match any cert SAN: srv1363566.hstgr.cloud
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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.profittolife.com/
200https://profittolife.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 87 ms lookup
PASS
1 A records, 87 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 187.77.18.224
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:4780:4:dab7::1
Info::
2 nameserver(s) configured
Got: ns2.dns-parking.com, ns1.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 87 ms
Got: 87 ms
A187.77.18.224
AAAA2a02:4780:4:dab7::1
CNAME—
NSns2.dns-parking.com, ns1.dns-parking.com
MX
5 mx1.hostinger.com
10 mx2.hostinger.com
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
profittolife.com
CAALookup not available with standard resolver
Resolved in 87 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

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 77ms across 3 resolvers (spread 92ms)
PASS
Mean 77ms across 3 resolvers (spread 92ms)
Info::
Google: 41ms
Got: 41ms via 8.8.8.8:53
Info::
Quad9: 57ms
Got: 57ms via 9.9.9.9:53
Info::
Cloudflare: 133ms
Got: 133ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://profittolife.com

https://profittolife.com

685 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://profittolife.com200685 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (94 ms)
PASS
IPv6 reachable (94 ms)
Info::
IPv6 is configured and reachable at 2a02:4780:4:dab7::1
Got: 94 ms connect
IPv6 Ready
AAAA Records 2a02:4780:4:dab7::1 Connection Reachable (94 ms)
A+
Crawlability
robots.txt present, sitemap with 26 URLs
PASS
robots.txt present, sitemap with 26 URLs
Info::
robots.txt is present
Got: 190 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 26 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 190 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /admin
Disallow: /admin/
Disallow: /api/
Disallow: /carrito
Disallow: /gracias

Host: https://profittolife.com
Sitemap: https://profittolife.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 26 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
profittolife.com — via Realtime Register B.V., 2 years, 9 months old
PASS
profittolife.com — via Realtime Register B.V., 2 years, 9 months old
Warning::
Domain expires in 77 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Dec 6, 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: Realtime Register B.V.
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

76 days

December 6, 2026

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

2 years, 9 months

Registered December 6, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:4:dab7::1

Registrar

Realtime Register B.V.

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 Realtime Register B.V.
Created December 6, 2023 (2 years, 9 months ago)
Expires December 6, 2026 (2 months)
Last Updated November 9, 2025
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 2a02:4780:4:dab7::1
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 89 ms TCP Connect 102 ms TLS Handshake 108 ms Server Processing 423 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback