Skip to content
https://xpenv.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
10 PASS 6 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3033::ac43:b529, 2606:4700:3034::6815:338c
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3033::ac43:b529]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2606:4700:3033::ac43:b529, 2606:4700:3034::6815:338c Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.51.140: lookup 104.21.51.140: 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.181.41: lookup 172.67.181.41: 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:3033::ac43:b529: lookup 2606:4700:3033::ac43:b529: 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:3034::6815:338c: lookup 2606:4700:3034::6815:338c: 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
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

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
B
CDN & Delivery
Cloudflare (EXPIRED)
REVIEW
Cloudflare (EXPIRED)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a02e52456aa042cc-EWR
Info::
CDN cache status: EXPIRED
CDN Detected: Cloudflare
Provider Cloudflare Cache Status EXPIRED Evidence cf-ray: a02e52456aa042cc-EWR
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
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.51.140, 172.67.181.41
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::ac43:b529, 2606:4700:3034::6815:338c
Info::
2 nameserver(s) configured
Got: jule.ns.cloudflare.com, benedict.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
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: 9 ms
Got: 9 ms
A104.21.51.140, 172.67.181.41
AAAA2606:4700:3033::ac43:b529, 2606:4700:3034::6815:338c
CNAME
NSjule.ns.cloudflare.com, benedict.ns.cloudflare.com
MX
20 route2.mx.cloudflare.net
86 route1.mx.cloudflare.net
93 route3.mx.cloudflare.net
TXT
stellar.toml=https://ipfs.io/ipfs/bafybeiepztegjxdecpkajo27mh2jwuvi3yaexkblmtx35...
CAALookup not available with standard resolver
Resolved in 9 ms

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
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Multi-Resolver DNS Speed
Mean 11ms across 3 resolvers (spread 14ms)
PASS
Mean 11ms across 3 resolvers (spread 14ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
Info::
Quad9: 16ms
Got: 16ms 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://xpenv.com

https://xpenv.com

43 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://xpenv.com20043 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 2291 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2291 B Sitemaps referenced 1 User-agents Amazonbot, Applebot-Extended, Bytespider, ClaudeBot, Google-Extended, GPTBot, meta-externalagent, *, CCBot, CloudflareBrowserRenderingCrawler Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

# XPENV.COM — crawler policy (classic robots directives for broad compatibility).

# Preference for indexing the public web app shell and static docs at this origin.



User-agent: *

Allow: /



# Former Content-Signals (ai-train / search / ai-input) appeared here for experimental agent awareness;

# they are omitted so strict robots validators (and tools like Lighthouse) accept this file verbatim.

# For transparency and indexing: see /.well-known/api-catalog , /sitemap.xml , and canonical HTML URLs.



Sitemap: https://xpenv.com/sitemap.xml


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

https://www.xpenv.com/
200https://xpenv.com/

HTTP → HTTPS

301http://xpenv.com/ https://xpenv.com/

Consistent

A+
Domain Intelligence
xpenv.com — via HOSTINGER operations, UAB, 19 days old
PASS
xpenv.com — via HOSTINGER operations, UAB, 19 days old
Info::
Domain registered until May 9, 2027 (11 months remaining)
Info::
Domain is only 19 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered May 9, 2026
Info::
DNSSEC is enabled
Info::
Registrar: HOSTINGER operations, UAB
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

343 days

May 9, 2027

SSL certificate

89 days

Issued by Google Trust Services

Domain age

19 days

Registered May 9, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3033::ac43:b529

Registrar

HOSTINGER operations, UAB

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar HOSTINGER operations, UAB
Created May 9, 2026 (19 days ago)
Expires May 9, 2027 (11 months)
Last Updated May 28, 2026
Name Servers benedict.ns.cloudflare.com, jule.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700:3033::ac43:b529
Data source: rdap (0.0s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

Connection waterfall

DNS Lookup 87 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 172 ms Content Transfer 1 ms
A+
CDN Cache Observability
Cache state: EXPIRED
PASS
Cache state: EXPIRED
Info::
CDN cache state observable via 2 header(s)
Got: age=46492, cf-cache-status=EXPIRED
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback