How We Protect Our Own Website: 5 Built-In Safeguards
A municipal security partner should hold itself to the same standard it checks on local government websites. Every build verifies our main-site headers, Content Security Policy, preview isolation, and RFC 9116 disclosure policy before deployment:
- Control 1: Enforced HTTPS, HSTS & Strict Content Security Policy.
- Every WebStand page on offtheclocksoftware.com enforces TLS 1.2/1.3 encryption, Strict-Transport-Security, clickjacking protection, disabled browser camera/microphone/geolocation permissions, and a strict Content Security Policy blocking unauthorized scripts.
- Control 2: Authenticated Outbound Mail (SPF, DKIM, DMARC & One-Click Unsubscribe).
- Our outbound mail domains publish SPF records, cryptographic DKIM signatures, and enforced DMARC policies, and every outreach message includes RFC 8058 one-click unsubscribe headers.
- Control 3: Zero End-of-Life Software & Zero Public Database Surface.
- Our studio pages pre-render to static HTML, CSS, and WebP assets at the Cloudflare edge with no public CMS database login page, zero third-party ad trackers, and self-hosted WOFF2 fonts.
- Control 4: Registrar Lock, Accountable Leadership & RFC 9116 security.txt.
- Led by Timothy Kennedy, Founder, CEO, and security lead. WebStand maintains registrar transfer locks and publishes a machine-readable disclosure policy at /.well-known/security.txt.
- Control 5: Tokenized, Non-Indexed Preview Isolation.
- Private municipal and client website previews live at unguessable tokenized paths, carry search-engine exclusion headers, and pass automated security readiness gates before every build.