How ServerNix Auditing Works
A deep technical breakdown of our 8-stage edge execution pipeline, non-destructive probing model, and weighted scoring formula.
Cloudflare Workers Edge Architecture
Autonomous edge execution without monolithic server clusters
Traditional website auditing tools rely on slow, centralized VPS clusters or headless browser scrapers that can hang, consume gigabytes of RAM, or trip rate limiters. ServerNix runs natively on Cloudflare Workers edge runtime. Audits execute via lightweight, asynchronous fetch streams that evaluate DNS records, SSL/TLS handshakes, HTTP response headers, and HTML DOM metadata in parallel across 300+ edge locations worldwide.
Every audit target is resolved against Cloudflare DNS-over-HTTPS (DoH) prior to connection. If a hostname resolves to a private IPv4 (e.g. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.1), link-local (169.254.0.0/16), or cloud metadata address (169.254.169.254), the request is rejected immediately at the edge. Redirect chains are manually inspected hop-by-hop to ensure target domains cannot pivot into private subnets.
Weighted Scoring Algorithm
Your final health score (0 to 100) is calculated using an objective, weighted mathematical formula across the 7 audit categories. Checks are assigned individual status values: Passed (100), Warning (50), or Failed (0). Category scores represent the average of all checks in that discipline.
| Category | Relative Weight | Focus Area |
|---|---|---|
| Security Headers & Exposures | 25% | HSTS, CSP, X-Frame-Options, cookie security flags, sensitive file protection |
| SEO Configuration | 20% | Titles, meta descriptions, robots.txt, sitemaps, Open Graph, canonical tags |
| Availability & Response | 15% | HTTP 200 OK status, edge response latency (TTFB), redirect loop prevention |
| SSL & HTTPS | 15% | TLS 1.2/1.3, certificate expiration buffer, HTTP-to-HTTPS redirect enforcement |
| Performance Indicators | 15% | HTML payload weight, Brotli/Gzip compression, Cache-Control headers |
| DNS & Email Security | 5% | Authoritative name servers, A/AAAA records, SPF & DMARC anti-spoofing |
| Technical Hygiene | 5% | HTML5 DOCTYPE, UTF-8 charset, mixed-content detection, Content-Type headers |
Detailed Category Inspections
What each verification test checks and why it directly influences user experience, search ranking, or defensive posture.
1. Availability & Edge Latency
Weight: 15%Verifies that the target responds with a valid HTTP 200 OK status code. Measures Time-to-First-Byte (TTFB) from the nearest edge worker. Inspects redirect chains to ensure no circular redirect loops exist and confirms that trailing slashes or subdomains resolve with fewer than 3 hops.
2. SSL & HTTPS Security
Weight: 15%Audits the active TLS certificate for expiration thresholds (flagging warnings if expiration is under 30 days and failures under 7 days). Validates that insecure TLS 1.0/1.1 protocols are disabled in favor of modern TLS 1.2 or 1.3. Ensures plaintext HTTP requests automatically redirect to secure HTTPS.
3. Security Headers & Exposures
Weight: 25% The heaviest-weighted category. Inspects HTTP response headers for Strict-Transport-Security (HSTS) with includeSubDomains and preload. Evaluates Content-Security-Policy (CSP), X-Frame-Options (DENY or SAMEORIGIN), X-Content-Type-Options: nosniff, and Referrer-Policy. Safe probes check that sensitive development files like /.env or /.git are strictly unreachable.
4. SEO Configuration
Weight: 20% Parses target HTML for canonical SEO signals: page title length (optimal 30–60 characters), meta description presence (optimal 70–160 characters), viewport responsiveness meta tags, favicon presence, Open Graph social tags (og:title, og:image), Twitter cards, H1 heading hierarchy, and robots.txt & XML sitemap availability.
5. Performance Indicators
Weight: 15%Evaluates raw HTML payload weight (flagging oversized documents over 2MB), HTTP Content-Encoding compression (verifying Brotli or Gzip activation), Cache-Control headers for static assets, and HTML resource counts (scripts, stylesheets, and images) that dictate mobile rendering speed.
6. DNS & Email Authentication
Weight: 5% Performs Cloudflare DoH queries to resolve authoritative DNS records: A (IPv4), AAAA (IPv6), CNAME, MX (mail exchange), and NS (nameservers). Inspects domain TXT records for SPF (v=spf1) and queries _dmarc.yourdomain.com for DMARC email spoofing defense.
7. Technical Hygiene
Weight: 5% Confirms modern web standards compliance: HTML5 <!DOCTYPE html> declaration, UTF-8 character encoding, proper Content-Type MIME type headers, and mixed-content detection (ensuring no insecure http:// scripts, styles, or iframes are loaded over HTTPS).
xAI Grok Remediation Synthesis
While raw telemetry gives engineers exact data, business stakeholders and agency clients often need an executive narrative. Our integration with xAI's Grok API analyzes the complete audit report, contextualizes risk severity, and returns high-level summaries alongside actionable code snippets for Apache, Nginx, Cloudflare, and Node.js servers.