Skip to content
https://xpenv.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
10 PASS 7 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.18.32.94: lookup 104.18.32.94: 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.64.155.162: lookup 172.64.155.162: 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:4405::ac40:9ba2: lookup 2606:4700:4405::ac40:9ba2: 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:4401::6812:205e: lookup 2606:4700:4401::6812:205e: 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
71 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

71
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
  • Enable DNSSEC on your domain for DNS spoofing protection
B
CDN & Delivery
Cloudflare (EXPIRED)
REVIEW
Cloudflare (EXPIRED)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a02786e29c6241e3-EWR
Info::
CDN cache status: EXPIRED
CDN Detected: Cloudflare
Provider Cloudflare Cache Status EXPIRED Evidence cf-ray: a02786e29c6241e3-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, 61 ms lookup
PASS
2 A records, 61 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.32.94, 172.64.155.162
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:4405::ac40:9ba2, 2606:4700:4401::6812:205e
Info::
2 nameserver(s) configured
Got: orbit.dns-parking.com, horizon.dns-parking.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 61 ms
Got: 61 ms
A104.18.32.94, 172.64.155.162
AAAA2606:4700:4405::ac40:9ba2, 2606:4700:4401::6812:205e
CNAME—
NSorbit.dns-parking.com, horizon.dns-parking.com
MX
20 route2.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 61 ms
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 34ms across 3 resolvers (spread 33ms)
PASS
Mean 34ms across 3 resolvers (spread 33ms)
Info::
Cloudflare: 13ms
Got: 13ms via 1.1.1.1:53
Info::
Quad9: 44ms
Got: 44ms via 9.9.9.9:53
Info::
Google: 46ms
Got: 46ms via 8.8.8.8: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

86 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://xpenv.com20086 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:4405::ac40:9ba2, 2606:4700:4401::6812:205e
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:4405::ac40:9ba2, 2606:4700:4401::6812:205e Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 553 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 553 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# 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
sitemap.xml 200 OK
Type URL Set URLs 7 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::
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, 18 days old
PASS
xpenv.com — via HOSTINGER operations, UAB, 18 days old
Info::
Domain registered until May 9, 2027 (11 months remaining)
Info::
Domain is only 18 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 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: 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

346 days

May 9, 2027

SSL certificate

71 days

Issued by Google Trust Services

Domain age

18 days

Registered May 9, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:4401::6812:205e

Registrar

HOSTINGER operations, UAB

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
  • 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 (18 days ago)
Expires May 9, 2027 (11 months)
Last Updated May 27, 2026
Name Servers horizon.dns-parking.com, orbit.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:4401::6812:205e
Data source: rdap (0.1s)

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.

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

Connection waterfall

DNS Lookup 71 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 342 ms Content Transfer 1 ms
A+
CDN Cache Observability
Cache state: EXPIRED
PASS
Cache state: EXPIRED
Info::
CDN cache state observable via 1 header(s)
Got: 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