WebStand.Security (419) 370-2996 Request an Assessment

WebStand Security · Policy Updated 1 November 2026

Web and Domain Security for Local Government.

We assess municipal websites, email domains, and public records from the outside, identify the exposures that cyber-insurance underwriters and attackers look for first, and deliver a clear remediation plan for your leadership and IT team.

How We Assess: Two Clear Tiers

We maintain a strict ethical and legal boundary between passive public-record assessment and authorized active testing. Every engagement begins on the outside and never crosses into municipal systems without signed written authorization.

1

Tier 1: Passive Public-Record Check

We inspect only what the public internet and cyber-insurance underwriters already see: public domain registration records, SPF and DMARC email authentication, TLS encryption and security headers, public software versions cross-checked against the CISA Known Exploited Vulnerabilities catalog, and redaction integrity inside publicly posted PDF packets. Every assessment runs through automated scanning, in-depth technical analysis to eliminate false alarms, and human verification by our team.

Free for Local Government
2

Tier 2: Authorized Deeper Testing

When your city, village, or township wants to evaluate specific portals, applications, or workflows beyond the public view, we conduct scoped security testing under written Rules of Engagement. Tier 2 testing is performed only with your signed authorization, only on the systems you designate, and includes a verification re-test after remediation.

Quoted in Writing First

What Our Tier 1 Passive Check Inspects — and What It Never Does

Mayors, city managers, clerks, law directors, and IT leaders deserve to know exactly how an external assessment works before requesting one. Here is our Tier 1 scope:

Public DNS & Email Anti-Spoofing (SPF, DKIM & DMARC).
We inspect your public mail authentication records to determine whether outside mail servers will reject forged emails claiming to come from your municipal domain.
Domain Governance & Forgotten Subdomains.
We check public domain registration status (expiration dates, registrar transfer locks, and .gov readiness) and public certificate logs to identify forgotten vendor, staging, or webmail subdomains.
Encrypted TLS Connections & Browser Security Headers.
We verify standard TLS 1.2/1.3 encryption and inspect public browser security headers — including Strict-Transport-Security, Content-Security-Policy, and clickjacking defenses.
Public Software Versions & CISA KEV Cross-Check.
We compare software version numbers exposed by the public website against the National Vulnerability Database and the CISA Known Exploited Vulnerabilities catalog.
Public PDF Packet Redaction & Accessibility.
We inspect publicly posted council packets, minutes, and forms for unflattened visual redactions (black boxes drawn over selectable text), hidden staff file-path metadata, and ADA Title II document tagging.
Strict Tier 1 Boundary (What We Never Do Without Written Authorization).
Tier 1 never sends exploit payloads, never guesses passwords or submits login forms, never scans non-web ports, and identifies automated checks transparently with our OTC-research/1.0 (+https://webstand.app) user-agent.

Cyber-Insurance & CISA Readiness

Municipal risk pools, cyber-insurance underwriters, and state grant evaluators routinely verify external domain and website posture from public records before issuing or renewing coverage. Our assessments evaluate the five areas underwriters check first:

1. Official .gov & Domain Governance.
Transition to an official .gov address or a registrar-locked domain with current renewal records, ensuring a lapsed registration or unauthorized DNS change cannot redirect residents.
2. Email Authentication (SPF & DMARC).
Published SPF and enforced DMARC policies on your municipal domain so outside mail servers block forged invoice, utility, or payroll emails sent in your city or township’s name.
3. Supported, Patched Web Platform.
Web servers and content management systems running actively supported releases, with zero exposures listed in the federal CISA Known Exploited Vulnerabilities catalog.
4. Enforced HTTPS, Modern TLS & Browser Protections.
Automatic HTTPS redirects on both the bare domain and www, current TLS encryption certificates, Strict-Transport-Security (HSTS), clickjacking protection, and Content Security Policy rules.
5. Administrative Isolation & True PDF Redaction.
Separation of staff sign-in portals from the public website, retirement of forgotten vendor subdomains, and true removal of selectable text layers and workstation metadata inside public PDF packets.

Self-Check Your Cyber-Insurance & .gov Readiness in 5 Easy Questions

Not sure what your municipal domain shows the public internet or a cyber-insurance underwriter today? Run through these 5 questions:

  1. Is your municipality on an official .gov domain, or registrar-locked with two-factor authentication on the domain registrar account?
  2. Does your public domain publish an enforced DMARC email policy so outside mail servers reject forged emails sent in your city or township’s name?
  3. Do both your bare domain and www redirect automatically to encrypted HTTPS connections with Strict-Transport-Security (HSTS) and a Content Security Policy?
  4. Is your public website running supported software free of CISA Known Exploited Vulnerabilities, with staff sign-in pages removed from public access?
  5. Have your publicly posted council packets and PDF forms been verified so blacked-out text cannot still be copied underneath visual boxes and internal staff file paths are stripped?

If the answer to any of these 5 questions is “no” or “I’m not sure”, Request Our Passive Security Check Below and we will verify all five from public records for your municipality.

What Your Municipality Receives

Every assessment produces two structured documents so elected officials, administrators, and technical staff each get exactly what they need without sifting through raw scanner noise:

Deliverable 1 · For Mayors, Council, Clerks & Underwriters

Executive Security & Cyber-Insurance Note

A concise executive brief written in plain English for mayors, council members, clerks, and city managers. Includes a 5-point Cyber-Insurance & Grant Readiness scorecard and findings organized into Action required, Worth checking, and Good news to keep.

Deliverable 2 · For Municipal IT & Web Vendors

Technical Appendix & Verification Ledger

The exact public DNS records, HTTP security headers, TLS certificate details, PDF metadata entries, and copy-paste configuration lines so your IT staff or current web vendor can remediate findings quickly.

Locked into an existing municipal website contract?

We provide standalone External Security, Cyber-Insurance & ADA Title II Readiness Assessments so your IT team or current vendor can close urgent gaps ahead of your next insurance renewal or audit — and if you transition to a WebStand Civic website within 12 months, 100% of the standalone assessment fee is credited toward your build.

What Our Passive Municipal Research Finds (379 Local Governments Screened)

Across our October 2026 passive public-record study of 379 small-city, village, and township websites, the most frequent exposures were domain governance and configuration gaps that can be resolved before an attacker or cyber-insurance underwriter flags them:

67%254 of 379 local governments still operate on commercial .com, .org, .net, or .us domains instead of an official .gov domain
24%92 of 379 run municipal website builds that have gone four or more years without an architecture or security refresh
12%44 of 379 expose web server or content-management software versions in public headers that have passed end-of-support
100%Every municipality surveyed faces the federal Department of Justice ADA Title II web and PDF accessibility rule (28 CFR Part 35)

Offline open-source CMS & civic plugin research: When our public-record screens identify content-management plugins and civic modules used by local governments, we audit their open-source code offline in isolated local environments and coordinate responsible disclosures through official MITRE CVE Numbering Authorities — never by testing against live municipal websites.

Inside an Executive Security & Cyber-Insurance Note (Preview)

Every Executive Security Note follows the same four-part structure so a mayor, city manager, clerk, or law director can read the executive summary in five minutes and hand the technical appendix straight to IT:

Part I & II · Executive Summary & 5-Control Scorecard

Exampleville (exampleville.gov.example) · Tier 1 Passive Posture Brief

1. Domain & Registrar
Action required: Operating on a commercial .org domain without registrar transfer lock; eligible to transition to an official .gov address.
2. Email Anti-Spoofing
Action required: SPF record present, but no DMARC policy record published; outside senders can forge @exampleville.gov.example.
3. Platform & CISA KEV
Good news to keep: Supported software release with zero exposures in the CISA Known Exploited Vulnerabilities catalog.
4. HTTPS, TLS & Headers
Worth checking: Valid TLS 1.3 certificate, but missing Strict-Transport-Security (HSTS) and Content-Security-Policy headers.
5. Subdomains & PDFs
Action required: One public council packet contains selectable text beneath a visual black rectangle overlay, and the staff CMS login page is publicly reachable.
Part III & IV · Recommended Order of Operations & Copy-Paste Fixes

Practical Remediation Roadmap for Municipal IT or Your Web Vendor

Same-Day DNS & Header Fixes
Publish a DMARC policy record in monitoring mode and add Strict-Transport-Security, clickjacking protection, and Content-Security-Policy response headers (exact copy-paste lines included in the Technical Appendix).
30-Day Document & Login Hygiene
Replace the council packet PDF with a truly redacted copy, strip workstation file paths before uploading future packets, and restrict public access to the staff sign-in page.
90-Day Governance Step
Complete the federal .gov domain registration and advance DMARC enforcement to quarantine or reject ahead of your next cyber-insurance renewal.

Sample Findings (Redacted)

Our executive security notes are written for municipal decision-makers and IT staff alike: no raw scanner dumps, no exploit instructions, and no alarmist language. Here are three redacted sample findings showing how we report issues:

Action Required · Email Authentication

Municipal Domain Allows Forged Outbound Email (DMARC Missing)

What We Saw
The public DNS records for exampleville.gov.example publish an SPF record, but no DMARC policy record exists.
Why It Matters
Without an enforced DMARC policy, outside mail servers cannot block an impersonator from forging @exampleville.gov.example on vendor payment, tax, or utility notices. Municipal cyber-insurance questionnaires verify this record directly in public DNS.
What Fixes It
Publish the DMARC TXT record provided in our Technical Appendix in monitoring mode first, confirm legitimate municipal mail services, and step enforcement up to quarantine or reject.
Action Required · Public Records Privacy

Visually Blacked-Out Text in a Public Council Packet Remains Selectable

What We Saw
A publicly posted council packet PDF contains black rectangle overlays drawn over sensitive account details, while the underlying text layer still retains the original characters.
Why It Matters
Anyone who downloads the public PDF can copy and paste the text underneath the visual box or locate it through a standard document search.
What Fixes It
Flatten redacted pages to images or apply true PDF redaction that permanently removes underlying text objects before publishing, and strip staff workstation file paths from document metadata.
Worth Checking · Administrative Surface

Administrator Sign-In and Legacy Webmail Exposed on the Public Website

What We Saw
The public website exposes its interactive content-management sign-in page and staff webmail portal to the open internet.
Why It Matters
Publicly reachable administrator login pages attract continuous automated password-guessing traffic and heighten the risk of a single reused credential.
What Fixes It
Serve the public municipal website from a decoupled static architecture with no public database login, or place staff sign-in behind multi-factor authentication and an access gate.

FAQ by Municipal Leaders & IT Teams

Does a Tier 1 Passive Assessment Touch Our Internal Network or Slow Down Our Website?

No. A Tier 1 assessment inspects only public records that are already visible on the open internet: your domain registration, public email authentication records (SPF and DMARC), standard encrypted browser connections, public software versions, and publicly posted PDF packets. It never sends exploit traffic, never tests login forms, and never touches internal municipal networks.

What Is the Difference Between Tier 1 and Tier 2 Security Testing?

Tier 1 is a zero-touch external assessment of what the public internet and cyber-insurance underwriters already see. Tier 2 is deeper, authorized security testing of specific municipal portals, applications, or workflows you ask us to evaluate, conducted only under signed written Rules of Engagement.

Why Do You Inspect Public PDF Packets on Municipal Websites?

Council packets, ordinances, and public forms frequently contain visual redactions where a black rectangle was drawn over sensitive account numbers without removing the selectable text layer underneath, or hidden file properties that expose staff usernames and internal network paths. We check for both alongside federal ADA Title II accessibility tagging.

How Does Your Assessment Help with Municipal Cyber-Insurance Renewals?

Municipal cyber-insurance underwriters routinely verify enforced DMARC email anti-spoofing, modern TLS encryption, HSTS browser protection, supported web software with zero CISA Known Exploited Vulnerabilities, and protected administrator sign-in pages. Our 5-control scorecard maps directly to those underwriting checks and gives your IT staff or web vendor exact configuration fixes.

Request a Free Security Presentation

Tell us your city, village, or township and your website address. We will run our free three-layer public security check and present the findings to your municipality (also available on WebStand Civic).

We use your details only to reply. Privacy

Request Deeper Security Testing

Want authorized Tier 2 testing beyond the public view or a standalone cyber-insurance readiness check? Tell us your municipality or organization, website or system, and what you want assessed, or call (419) 370-2996.

Authorized testing only with written permission. Privacy

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.

How to Report a Security Issue

If you discover a security issue in our own website or services, please report it so we can resolve it promptly. Email [email protected] with the subject line “Security report”, or call or text Tim at (419) 370-2996 if the matter is urgent. Our machine-readable policy is published at /.well-known/security.txt (RFC 9116).

Please include:

  • The web address (URL) or endpoint where you observed the issue
  • Clear steps to reproduce it, or a minimal proof of concept
  • The potential impact if exploited
  • How you would like to be credited (or if you prefer to remain anonymous)

We reply within 2 business days to confirm receipt of your report, and we provide our assessment and remediation plan within 5 business days. Please allow up to 30 days for us to verify and remediate an issue before public disclosure.

What Is in Scope

  • This website (offtheclocksoftware.com) and its first-party endpoints (/api/contact, /api/unsubscribe, and /api/shop/*)
  • Our own sample websites under /demos/*
  • First-party software and portals operated directly by Off the Clock Software LLC

Good-Faith Safe Harbor

If you follow the rules on this page in good faith — testing only in-scope systems, respecting rate limits, never accessing or modifying another person’s or municipality’s data, and reporting findings directly to us — we treat your research as authorized. We will not initiate legal action against you or refer your report to law enforcement.

What Is Out of Scope

  • Client, municipal and prospect websites or previews: Never test a city, village, township or business website, or a private business preview (/<slug>-<token>/), unless that organization has given you separate written permission.
  • Stop and report immediately: As soon as you prove an issue exists, stop. Never read, copy, change or delete another person’s or business’s data, preview or messages.
  • No service disruption or spam: Do not run denial-of-service attacks, flood our forms, or send automated traffic faster than 5 requests per second.
  • No social engineering or physical testing: Do not phish, call or text our team, clients or partners under false pretences.
  • Third-party services: Do not test Cloudflare, Stripe, Resend, Zoho, GitHub or Google infrastructure itself under this policy.

Recognition

With your permission, we credit verified security reports in our acknowledgements section below once the issue is fixed. We are a small company and do not pay cash bounties under this stage of our policy; please do not test if you expect a payment.

Security Acknowledgements

We thank researchers who report valid security issues under this policy and list them here with their permission after a fix is live. No external reports have been published yet.

Request AssessmentCall