Skip to content
https://infoxnex.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
17
7 PASS 10 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 198.202.211.1: lookup 198.202.211.1: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 0 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.infoxnex.com/
200https://infoxnex.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://infoxnex.com/ https://infoxnex.com/

Consistent

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

Certificate validity

43
days left
0d 30d 60d 90d+

Recommended actions

  • 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 (BYPASS)
REVIEW
Cloudflare (BYPASS)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: a232f7caba56d84b-SJC
Info::
CDN cache status: BYPASS
CDN Detected: Cloudflare
Provider Cloudflare Cache Status BYPASS Evidence cf-ray: a232f7caba56d84b-SJC
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
1 A records, 35 ms lookup
PASS
1 A records, 35 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.202.211.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns57.domaincontrol.com, ns58.domaincontrol.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 35 ms
Got: 35 ms
A198.202.211.1
AAAA
CNAME
NSns57.domaincontrol.com, ns58.domaincontrol.com
MX
0 infoxnex-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 35 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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 12ms across 3 resolvers (spread 14ms)
PASS
Mean 12ms across 3 resolvers (spread 14ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Quad9: 17ms
Got: 17ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 363 ms total
PASS
1 redirect(s), 363 ms total
Info::
Single redirect
Got: https://infoxnex.com → https://www.infoxnex.com/ (301)
Info::
WWW normalization redirect

https://infoxnex.com

209 ms · HTTP/1.1

301

https://www.infoxnex.com/

155 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infoxnex.com301209 msHTTP/1.1cloudflare
2https://www.infoxnex.com/200155 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Domain Intelligence
infoxnex.com — via GoDaddy.com, LLC, 10 months old, hosted on Cloudflare
PASS
infoxnex.com — via GoDaddy.com, LLC, 10 months old, hosted on Cloudflare
Warning::
Domain expires in 38 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Sep 6, 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: 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: Cloudflare
Got: AS209242
Domain expiry

28 days

September 6, 2026

SSL certificate

43 days

Issued by Google Trust Services

Domain age

10 months

Registered September 6, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

198.202.211.1

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created September 6, 2025 (10 months ago)
Expires September 6, 2026 (1 months)
Last Updated October 16, 2025
Name Servers ns57.domaincontrol.com, ns58.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 198.202.211.1
ASN AS209242 (CLOUDFLARESPECTRUM - Cloudflare London, LLC, US)
Provider Cloudflare
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

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

Send Feedback