Skip to content
https://www.jcl.energy

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 6 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.
B
Reverse DNS
0/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 52.85.47.54 does not match any cert SAN: server-52-85-47-54.lhr86.r.cloudfront.net
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 52.85.47.111 does not match any cert SAN: server-52-85-47-111.lhr86.r.cloudfront.net
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 52.85.47.26 does not match any cert SAN: server-52-85-47-26.lhr86.r.cloudfront.net
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 52.85.47.20 does not match any cert SAN: server-52-85-47-20.lhr86.r.cloudfront.net
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 lookup failed for 2600:9000:2038:c000:0:e6ad:56c0:93a1: lookup 2600:9000:2038:c000:0:e6ad:56c0:93a1: 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 2600:9000:2038:9600:0:e6ad:56c0:93a1: lookup 2600:9000:2038:9600:0:e6ad:56c0:93a1: 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 2600:9000:2038:c400:0:e6ad:56c0:93a1: lookup 2600:9000:2038:c400:0:e6ad:56c0:93a1: 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 2600:9000:2038:8000:0:e6ad:56c0:93a1: lookup 2600:9000:2038:8000:0:e6ad:56c0:93a1: 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 2600:9000:2038:a400:0:e6ad:56c0:93a1: lookup 2600:9000:2038:a400:0:e6ad:56c0:93a1: 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 2600:9000:2038:2c00:0:e6ad:56c0:93a1: lookup 2600:9000:2038:2c00:0:e6ad:56c0:93a1: 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 2600:9000:2038:7e00:0:e6ad:56c0:93a1: lookup 2600:9000:2038:7e00:0:e6ad:56c0:93a1: 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 2600:9000:2038:3600:0:e6ad:56c0:93a1: lookup 2600:9000:2038:3600:0:e6ad:56c0:93a1: 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
HTTP Probe Timing
Total 879 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
67 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
26 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
30 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
703 ms
Total Time Total request time from DNS lookup through full response.
879 ms

Connection waterfall

DNS Lookup 67 ms TCP Connect 26 ms TLS Handshake 30 ms Server Processing 580 ms Content Transfer 177 ms
B
TLS Certificate Expiry & Recommendations
170 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

170
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.
A
DNS Records
4 A records, 44 ms lookup
PASS
4 A records, 44 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.85.47.54, 52.85.47.111, 52.85.47.26, 52.85.47.20
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2038:c000:0:e6ad:56c0:93a1, 2600:9000:2038:9600:0:e6ad:56c0:93a1, 2600:9000:2038:c400:0:e6ad:56c0:93a1, 2600:9000:2038:8000:0:e6ad:56c0:93a1, 2600:9000:2038:a400:0:e6ad:56c0:93a1, 2600:9000:2038:2c00:0:e6ad:56c0:93a1, 2600:9000:2038:7e00:0:e6ad:56c0:93a1, 2600:9000:2038:3600:0:e6ad:56c0:93a1
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d1gicmljencevv.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1370.awsdns-43.org, ns-2025.awsdns-61.co.uk, ns-352.awsdns-44.com, ns-856.awsdns-43.net
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 44 ms
Got: 44 ms
A52.85.47.54, 52.85.47.111, 52.85.47.26, 52.85.47.20
AAAA2600:9000:2038:c000:0:e6ad:56c0:93a1, 2600:9000:2038:9600:0:e6ad:56c0:93a1, 2600:9000:2038:c400:0:e6ad:56c0:93a1, 2600:9000:2038:8000:0:e6ad:56c0:93a1, 2600:9000:2038:a400:0:e6ad:56c0:93a1, 2600:9000:2038:2c00:0:e6ad:56c0:93a1, 2600:9000:2038:7e00:0:e6ad:56c0:93a1, 2600:9000:2038:3600:0:e6ad:56c0:93a1
CNAMEd1gicmljencevv.cloudfront.net
NSns-1370.awsdns-43.org, ns-2025.awsdns-61.co.uk, ns-352.awsdns-44.com, ns-856.awsdns-43.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 44 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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+
Subdomain Takeover
CNAME points at managed service(s) — verify configuration
PASS
CNAME points at managed service(s) — verify configuration
Info::
CNAME targets AWS CloudFront — verify ownership
CNAME targets CloudFront. Distribution names are GUID-style so accidental re-registration is unlikely, but a deleted distribution will return errors. Verify the CloudFront distribution is still active.
Got: d1gicmljencevv.cloudfront.net
A+
Multi-Resolver DNS Speed
Mean 47ms across 3 resolvers (spread 33ms)
PASS
Mean 47ms across 3 resolvers (spread 33ms)
Info::
Cloudflare: 26ms
Got: 26ms via 1.1.1.1:53
Info::
Google: 58ms
Got: 58ms via 8.8.8.8:53
Info::
Quad9: 59ms
Got: 59ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.jcl.energy

https://www.jcl.energy

537 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.jcl.energy200537 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2600:9000:2038:c000:0:e6ad:56c0:93a1, 2600:9000:2038:9600:0:e6ad:56c0:93a1, 2600:9000:2038:c400:0:e6ad:56c0:93a1, 2600:9000:2038:8000:0:e6ad:56c0:93a1, 2600:9000:2038:a400:0:e6ad:56c0:93a1, 2600:9000:2038:2c00:0:e6ad:56c0:93a1, 2600:9000:2038:7e00:0:e6ad:56c0:93a1, 2600:9000:2038:3600:0:e6ad:56c0:93a1
Got: 26 ms connect
IPv6 Ready
AAAA Records 2600:9000:2038:c000:0:e6ad:56c0:93a1, 2600:9000:2038:9600:0:e6ad:56c0:93a1, 2600:9000:2038:c400:0:e6ad:56c0:93a1, 2600:9000:2038:8000:0:e6ad:56c0:93a1, 2600:9000:2038:a400:0:e6ad:56c0:93a1, 2600:9000:2038:2c00:0:e6ad:56c0:93a1, 2600:9000:2038:7e00:0:e6ad:56c0:93a1, 2600:9000:2038:3600:0:e6ad:56c0:93a1 Connection Reachable (26 ms)
A+
Crawlability
robots.txt present, sitemap with 88 URLs
PASS
robots.txt present, sitemap with 88 URLs
Info::
robots.txt is present
Got: 658 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 88 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 658 B Sitemaps referenced 1 User-agents ClaudeBot, Google-Extended, CCBot, *, OAI-SearchBot, PerplexityBot, Perplexity-User, ChatGPT-User, Claude-User, Claude-SearchBot, Applebot-Extended, meta-externalagent, Google-CloudVertexBot, GPTBot, Amazonbot, cohere-ai, DuckAssistBot Blocking No — crawling allowed
# START nuxt-robots (indexable)
# AI answer engines and training crawlers (see config/robots.ts).
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Claude-SearchBot
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: DuckAssistBot
User-agent: Google-CloudVertexBot
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: meta-externalagent
User-agent: Amazonbot
User-agent: CCBot
User-agent: cohere-ai
Allow: /
Disallow: /v1/
Disallow: /site/

User-agent: *
Disallow: /v1/
Disallow: /site/

Sitemap: https://www.jcl.energy/sitemap.xml
# END nuxt-robots
sitemap.xml 200 OK
Type URL Set URLs 88 entries Valid XML Yes
Sample URLs:
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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.jcl.energy/
301https://jcl.energy/

Preferred variant: www

HTTP → HTTPS

301http://www.jcl.energy/ → https://www.jcl.energy/

Consistent

A+
Domain Intelligence
jcl.energy — via GoDaddy.com, LLC, 7 years, 11 months old
PASS
jcl.energy — via GoDaddy.com, LLC, 7 years, 11 months old
Info::
Domain registered until Nov 9, 2027 (1 years, 1 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: 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

414 days

November 9, 2027

SSL certificate

170 days

Issued by Amazon

Domain age

7 years, 11 months

Registered November 9, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:2111:9800:0:e6ad:56c0:93a1

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created November 9, 2018 (7 years, 11 months ago)
Expires November 9, 2027 (1 years, 1 months)
Last Updated August 27, 2026
Name Servers monika.ns.cloudflare.com, felicity.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2600:9000:2111:9800:0:e6ad:56c0:93a1
Data source: rdap (0.4s)

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
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Document is served via AWS CloudFront CDN (edge: LHR86-P3)
Got: delegation d1gicmljencevv.cloudfront.net
Info::
CDN cache status: Miss from cloudfront
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence delegation d1gicmljencevv.cloudfront.net
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
A+
Health Check Endpoint
Health endpoint at https://www.jcl.energy/health (HTTP 200)
PASS
Health endpoint at https://www.jcl.energy/health (HTTP 200)
Info::
Public health endpoint at https://www.jcl.energy/health
Got: https://www.jcl.energy/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback