Skip to content
https://ajfreshxxx.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
11 PASS 6 REVIEW
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.2.126: lookup 104.21.2.126: 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.152.203: lookup 172.67.152.203: 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:3031::ac43:98cb: lookup 2606:4700:3031::ac43:98cb: 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:3035::6815:27e: lookup 2606:4700:3035::6815:27e: 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
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 301-redirects to HTTPS

www / non-www

200https://www.ajfreshxxx.com/
200https://ajfreshxxx.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

52
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
  • 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
2 A records, 14 ms lookup
PASS
2 A records, 14 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.2.126, 172.67.152.203
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3031::ac43:98cb, 2606:4700:3035::6815:27e
Info::
2 nameserver(s) configured
Got: dina.ns.cloudflare.com, micah.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
SPF record present in TXT
Info::
DNS resolution time: 14 ms
Got: 14 ms
A104.21.2.126, 172.67.152.203
AAAA2606:4700:3031::ac43:98cb, 2606:4700:3035::6815:27e
CNAME—
NSdina.ns.cloudflare.com, micah.ns.cloudflare.com
MX—
TXT
SPF v=spf1 -all
google-site-verification=--CaN0enWUZCbTEOw91s6LH7kvCzfb3fzTJTe3bgdmg
CAALookup not available with standard resolver
Resolved in 14 ms
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 10ms across 3 resolvers (spread 14ms)
PASS
Mean 10ms across 3 resolvers (spread 14ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 14ms
Got: 14ms via 9.9.9.9:53
Info::
Google: 16ms
Got: 16ms 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://ajfreshxxx.com

https://ajfreshxxx.com

206 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ajfreshxxx.com200206 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3031::ac43:98cb, 2606:4700:3035::6815:27e
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3031::ac43:98cb, 2606:4700:3035::6815:27e Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 1237 URLs
PASS
robots.txt present, sitemap with 1237 URLs
Info::
robots.txt is present
Got: 14 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1237 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 14 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
sitemap.xml 200 OK
Type URL Set URLs 1237 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ajfreshxxx.com — via Cloudflare, Inc., 2 years, 8 months old
PASS
ajfreshxxx.com — via Cloudflare, Inc., 2 years, 8 months old
Info::
Domain registered until Nov 22, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, Inc.
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

105 days

November 22, 2026

SSL certificate

52 days

Issued by Google Trust Services

Domain age

2 years, 8 months

Registered November 22, 2023

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3031::ac43:98cb

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created November 22, 2023 (2 years, 8 months ago)
Expires November 22, 2026 (3 months)
Last Updated October 23, 2025
Name Servers dina.ns.cloudflare.com, micah.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700:3031::ac43:98cb
Data source: rdap (0.3s)

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 210 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 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.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
209 ms
Total Time Total request time from DNS lookup through full response.
210 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 2 ms TLS Handshake 9 ms Server Processing 189 ms Content Transfer 1 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a23ae00b6b473418-EWR
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a23ae00b6b473418-EWR
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback