CyberShield™ · Written Security Audit · Real Sample
Real Sample Report — live audit of skillquesters.com, November 15, 2026
Summary — what we found first
The site’s encryption, email protection and exposed-file defenses are in good shape: modern TLS only, a valid Let’s Encrypt certificate, DMARC and DKIM published, and the classic sensitive files (.git, .env) blocked. Three real findings remain, in fix order: (1) no Content-Security-Policy header is sent, (2) the www address takes a detour through plain HTTP in its redirect chain, (3) the one cookie the home page sets is missing its Secure and HttpOnly flags. Details and the measured evidence are layer by layer below.
Layer 1 — Encryption in transit (HTTPS & TLS) REAL
Result — Modern TLS only, valid certificate • Pass
What we measured: Plain HTTP requests to skillquesters.com are answered with a 301 redirect to the HTTPS address. The certificate is issued by Let’s Encrypt (issuer CN=YE1), covers skillquesters.com and www.skillquesters.com, and is valid from November 7, 2026 to February 5, 2027. A test connection negotiated TLS 1.3 (cipher TLS_AES_256_GCM_SHA384). Forced-connection tests: TLS 1.2 accepted; TLS 1.0 and TLS 1.1 rejected.
Why it matters, in plain words: Old TLS versions have known weaknesses; refusing them means visitors’ browsers always use a modern encrypted connection, and the certificate proves the site is the real one.
Finding 1.1 — The www address detours through plain HTTP • Moderate
What we measured: https://www.skillquesters.com/ answers 301 to http://skillquesters.com/ — plain HTTP — which then 301-redirects again to the HTTPS address. Two redirects, and the middle hop is unencrypted.
Why it matters, in plain words: For one step of the trip, the visitor’s request travels without encryption and could be tampered with on hostile Wi-Fi. The HSTS header (Layer 2) limits the damage in modern browsers, but the chain should not exist.
The fix: Point the www redirect straight at the HTTPS address. One line of server configuration.
Layer 2 — Security headers REAL
Result — Five protective headers are sent • Pass
What we measured (response headers of the home page, November 15, 2026):
| Header | Value sent |
|---|---|
| Strict-Transport-Security | max-age=31536000; includeSubDomains |
| X-Frame-Options | SAMEORIGIN |
| X-Content-Type-Options | nosniff |
| Referrer-Policy | strict-origin-when-cross-origin |
| Permissions-Policy | geolocation=(), microphone=(), camera=(), payment=() |
Why it matters, in plain words: Together these tell browsers: always use HTTPS for a year, do not frame this site inside another site, do not guess file types, do not leak full page addresses to other sites, and do not let the page use the camera, microphone, location or payment APIs at all.
Finding 2.1 — No Content-Security-Policy header • High priority
What we measured: The home page response contains no Content-Security-Policy header.
Why it matters, in plain words: A CSP is the browser-level allowlist of where scripts and styles may load from. Without one, if any script injection ever slipped into a page, the browser would have no second line of defense to stop it running.
The fix: Publish a CSP, starting in report-only mode to catch breakages, then enforce it. This is the highest-value change in this report.
Layer 3 — Cookies REAL
Finding 3.1 — The home page cookie is missing Secure and HttpOnly • Moderate
What we measured: The home page sets exactly one cookie, named sq-cc (the site’s own support-chat cookie), with Path=/ and SameSite=Lax — but without the Secure flag and without the HttpOnly flag.
Why it matters, in plain words: Without Secure, the browser may also send the cookie over a plain HTTP connection; without HttpOnly, page scripts can read it. SameSite=Lax already blocks most cross-site sending, so this is a hardening gap, not an open door.
The fix: Add the Secure and HttpOnly flags where the cookie is set.
Layer 4 — Sensitive paths & files REAL
Result — Sensitive files blocked, WordPress entry points closed • Pass
What we measured (HTTP status for each path, November 15, 2026):
| Path | Result | Meaning |
|---|---|---|
| /.git/HEAD | 403 Forbidden | Source-control data is blocked by server rules |
| /.git/config | 403 Forbidden | Blocked |
| /.env | 403 Forbidden | Environment file (secrets) is blocked |
| /xmlrpc.php | 404 Not Found | Nothing answers at this address |
| /wp-login.php | 404 Not Found | No login page answers at the standard WordPress address |
| /wp-admin/ | 404 Not Found | No admin area answers at the standard WordPress address |
| /.well-known/security.txt | 200 OK | Security contact published: contact@skillquesters.com (file expires November 14, 2027) |
Why it matters, in plain words: Automated scanners probe every site for exactly these addresses. Here they find a locked door or nothing at all — and a published security.txt tells honest researchers where to report a problem.
Layer 5 — Email protection (DNS) REAL
Result — SPF, DKIM, DMARC and CAA all published • Pass, one minor note
What we measured (DNS records of skillquesters.com, November 15, 2026):
| Record | Published value |
|---|---|
| SPF | v=spf1 a mx include:_spf.porkbun.com ~all |
| DKIM | Public key published at default._domainkey (v=DKIM1, RSA) |
| DMARC | v=DMARC1; p=quarantine; rua=mailto:skillquesters@gmail.com |
| Mail routing (MX) | 10 fwd1.porkbun.com · 20 fwd2.porkbun.com |
| CAA | Only letsencrypt.org may issue certificates; issuewild restricted the same way; iodef contact set |
Why it matters, in plain words: DMARC at p=quarantine tells receiving mail servers to junk spoofed mail that pretends to come from this domain, DKIM signs real outgoing mail, and CAA stops any other certificate authority from issuing a certificate for the domain.
Minor note: The SPF record ends in ~all (softfail) rather than -all (hard fail). With DMARC already at quarantine this is a small residual gap; the fix is to confirm every legitimate sender is covered, then tighten ~all to -all.
Your fix order (as it appears at the end of every report)
- Add a Content-Security-Policy header, report-only first (Finding 2.1).
- Point the www redirect straight at the HTTPS address (Finding 1.1).
- Add Secure and HttpOnly to the sq-cc cookie (Finding 3.1).
- Tighten SPF from ~all to -all once all senders are confirmed (Layer 5 note).
Prefer not to do this yourself? Every report ends with a fixed quote for Setup Done For You (from $299), and the optional Care Plan ($49/mo) keeps the checks running. Your call — the report is yours either way.
REAL SAMPLE — this report was generated on November 15, 2026 from live external checks of skillquesters.com, the publisher’s own site, and every measurement above is the actual result. A customer report covers the customer’s own site and questionnaire layers (passwords, updates, backups, staff access) as well; we never ask for your passwords.