← Back to SGS UniversityPractical Guide

Understanding Your Scan Results

Learn how to interpret common SiteGuardScan findings and decide what to fix first.

Guide Overview

A website scan can show several technical findings. Some are urgent, some are good improvements, and some require careful testing before changes are made. This guide helps non-technical users understand common categories without panic.

AdvertisementAd space reserved for guide content.

Common Findings

Missing HTTPS or Weak Redirect

If your site can load over HTTP, visitors may reach an insecure version. Fixing HTTPS and redirects should usually be a high priority.

Missing HSTS

HSTS tells browsers to use HTTPS automatically after the first secure visit. Enable it carefully, especially if you use subdomains.

Missing X-Frame-Options

This may mean your site can be embedded in another site. Frame protection helps reduce clickjacking risk.

Missing X-Content-Type-Options

This header helps prevent browsers from guessing file types in unsafe ways. It is commonly set to nosniff.

DNS and Email Findings

DNS findings may affect website availability, domain trust, and email delivery. Review old records and email authentication settings.

How to Prioritize Fixes

  • Fix HTTPS and certificate problems first.
  • Protect login and admin pages.
  • Add core security headers carefully.
  • Review DNS records and remove old entries.
  • Test the website after every change.

Quick Quiz

1. Which is usually higher priority: HTTPS failure or a minor informational note?

2. Why should changes be tested after deployment?

3. What does X-Frame-Options help reduce?

Run Another Scan