Skip to content
https://www.climeup.ai

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
17
8 PASS 8 REVIEW 1 FIX
D
HTTP Probe Timing
Action
Total 2658 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.66 s
Total Time Total request time from DNS lookup through full response.
2.66 s

Connection waterfall

DNS Lookup 60 ms TCP Connect 16 ms TLS Handshake 24 ms Server Processing 2.56 s Content Transfer 0 ms
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 3.162.38.53 does not match any cert SAN: server-3-162-38-53.cdg52.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 3.162.38.39 does not match any cert SAN: server-3-162-38-39.cdg52.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 3.162.38.55 does not match any cert SAN: server-3-162-38-55.cdg52.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 3.162.38.94 does not match any cert SAN: server-3-162-38-94.cdg52.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:262a:c800:1c:3846:5c0:93a1: lookup 2600:9000:262a:c800:1c:3846:5c0: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:262a:600:1c:3846:5c0:93a1: lookup 2600:9000:262a:600:1c:3846:5c0: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:262a:1400:1c:3846:5c0:93a1: lookup 2600:9000:262a:1400:1c:3846:5c0: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:262a:4a00:1c:3846:5c0:93a1: lookup 2600:9000:262a:4a00:1c:3846:5c0: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:262a:c00:1c:3846:5c0:93a1: lookup 2600:9000:262a:c00:1c:3846:5c0: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:262a:1000:1c:3846:5c0:93a1: lookup 2600:9000:262a:1000:1c:3846:5c0: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:262a:3c00:1c:3846:5c0:93a1: lookup 2600:9000:262a:3c00:1c:3846:5c0: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:262a:4000:1c:3846:5c0:93a1: lookup 2600:9000:262a:4000:1c:3846:5c0: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
Redirect Chain
1 redirect(s), 1487 ms total
REVIEW
1 redirect(s), 1487 ms total
Info::
Single redirect
Got: https://www.climeup.ai → https://www.climeup.ai/en (307)
Warning::
Redirect overhead: 1487 ms total
Got: 1487 ms

https://www.climeup.ai

193 ms · HTTP/1.1

307

https://www.climeup.ai/en

1294 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.climeup.ai307193 msHTTP/1.1
2https://www.climeup.ai/en2001294 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

C
Crawlability
Action
robots.txt present, sitemap with 2 URLs
REVIEW
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 49 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 49 B Sitemaps referenced 1 User-agents * Blocking Yes — all crawlers blocked
User-Agent: *
Disallow: /

Sitemap: /sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 2 entries Valid XML Yes
Sample URLs:
B
TLS Certificate Expiry & Recommendations
244 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

244
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
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
4 A records, 40 ms lookup
PASS
4 A records, 40 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.162.38.53, 3.162.38.39, 3.162.38.55, 3.162.38.94
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:262a:c800:1c:3846:5c0:93a1, 2600:9000:262a:600:1c:3846:5c0:93a1, 2600:9000:262a:1400:1c:3846:5c0:93a1, 2600:9000:262a:4a00:1c:3846:5c0:93a1, 2600:9000:262a:c00:1c:3846:5c0:93a1, 2600:9000:262a:1000:1c:3846:5c0:93a1, 2600:9000:262a:3c00:1c:3846:5c0:93a1, 2600:9000:262a:4000:1c:3846:5c0: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: dnhpcr08caryv.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-958.awsdns-55.net, ns-155.awsdns-19.com, ns-1454.awsdns-53.org, ns-2014.awsdns-59.co.uk
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: 40 ms
Got: 40 ms
A3.162.38.53, 3.162.38.39, 3.162.38.55, 3.162.38.94
AAAA2600:9000:262a:c800:1c:3846:5c0:93a1, 2600:9000:262a:600:1c:3846:5c0:93a1, 2600:9000:262a:1400:1c:3846:5c0:93a1, 2600:9000:262a:4a00:1c:3846:5c0:93a1, 2600:9000:262a:c00:1c:3846:5c0:93a1, 2600:9000:262a:1000:1c:3846:5c0:93a1, 2600:9000:262a:3c00:1c:3846:5c0:93a1, 2600:9000:262a:4000:1c:3846:5c0:93a1
CNAMEdnhpcr08caryv.cloudfront.net
NSns-958.awsdns-55.net, ns-155.awsdns-19.com, ns-1454.awsdns-53.org, ns-2014.awsdns-59.co.uk
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 40 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: dnhpcr08caryv.cloudfront.net
A+
Multi-Resolver DNS Speed
Mean 28ms across 3 resolvers (spread 16ms)
PASS
Mean 28ms across 3 resolvers (spread 16ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 30ms
Got: 30ms via 1.1.1.1:53
Info::
Quad9: 36ms
Got: 36ms via 9.9.9.9:53
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2600:9000:262a:c800:1c:3846:5c0:93a1, 2600:9000:262a:600:1c:3846:5c0:93a1, 2600:9000:262a:1400:1c:3846:5c0:93a1, 2600:9000:262a:4a00:1c:3846:5c0:93a1, 2600:9000:262a:c00:1c:3846:5c0:93a1, 2600:9000:262a:1000:1c:3846:5c0:93a1, 2600:9000:262a:3c00:1c:3846:5c0:93a1, 2600:9000:262a:4000:1c:3846:5c0:93a1
Got: 16 ms connect
IPv6 Ready
AAAA Records 2600:9000:262a:c800:1c:3846:5c0:93a1, 2600:9000:262a:600:1c:3846:5c0:93a1, 2600:9000:262a:1400:1c:3846:5c0:93a1, 2600:9000:262a:4a00:1c:3846:5c0:93a1, 2600:9000:262a:c00:1c:3846:5c0:93a1, 2600:9000:262a:1000:1c:3846:5c0:93a1, 2600:9000:262a:3c00:1c:3846:5c0:93a1, 2600:9000:262a:4000:1c:3846:5c0:93a1 Connection Reachable (16 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.climeup.ai/
https://climeup.ai/

HTTP → HTTPS

301http://www.climeup.ai/ → https://www.climeup.ai/

Consistent

A+
Domain Intelligence
climeup.ai — via GoDaddy.com, LLC, 4 years, 3 months old, hosted on AWS
PASS
climeup.ai — via GoDaddy.com, LLC, 4 years, 3 months old, hosted on AWS
Info::
Domain registered until Apr 10, 2032 (5 years, 10 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

2099 days

April 10, 2032

SSL certificate

244 days

Issued by Amazon

Domain age

4 years, 3 months

Registered April 10, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.33.251.168

Registrar

GoDaddy.com, LLC

Unlocked 4 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 April 10, 2022 (4 years, 3 months ago)
Expires April 10, 2032 (5 years, 10 months)
Last Updated April 2, 2025
Name Servers ns17.domaincontrol.com, ns18.domaincontrol.com, ns29.domaincontrol.com, ns30.domaincontrol.com
DNSSEC Not enabled
Registrant Registration Private
Hosting
IP Address 3.33.251.168
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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::
Site is served via AWS CloudFront CDN (edge: CDG52-P6)
Got: x-amz-cf-id: YMl5a60-I1Mp2tHSrvcoDHT92yLGnoTfQ1xVhemU6CfHgFkPc2X5Iw==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: YMl5a60-I1Mp2tHSrvcoDHT92yLGnoTfQ1xVhemU6CfHgFkPc2X5Iw==
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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback