When to run another scan (deploys, DNS, or a new app)
A short playbook for coming back to Scorifya after the kinds of changes that usually move TLS, headers, or mail DNS—so your score matches what visitors actually see.
Why rescans beat guessing
Public posture is whatever unauthenticated visitors fetch today—not what your dashboard says should happen after last week’s rollout.
A second pass catches regressions early: headers stripped at the CDN, redirects split across hosts, or mail authentication drifting after a DNS vendor cutover.
Make it a habit
Pair Scorifya with your release checklist the same way you’d re-run smoke tests: deploy → scan the canonical URL → fix anything new → scan once more after caches settle.
If you save domains on your watch list, automatic weekly passes keep a baseline fresh—but an on-demand scan right after you ship still catches drift between those passes.
Where to start
Use the homepage scanner with the hostname or full HTTPS URL customers load. From your account watch list you can confirm when you want another immediate pass.
For weights, caps, and scope reminders, keep how Scorifya works next to every report.
Try a scan on scorifya.com, read how we score, or see Pro for unlimited scans and exports.