Skip to main content

Security report for williamsburg.org

Other · N/a

Medium risk. 10 critical or high findings in Security headers, GDPR outside view and 3 other checks.

Security score

61/100

Risk levelMedium

0–100, higher is better. How it is calculated

The website at williamsburg.org/lander is currently a minimal content placeholder or domain parking page with no substantive business information or user-facing content. The domain is long-established, registered since 1996 with Network Solutions, LLC, and protected against unauthorized transfers. The site loads basic scripts related to Google Adsense and parking-lander functionality but lacks any privacy, cookie, or terms of service policies, contact information, or branding elements. Technically, the site uses JavaScript and CSS assets hosted on wsimg.com and includes Adsense scripts, indicating monetization attempts via advertising. However, no modern CMS or frameworks are detected, and SEO and accessibility features are minimal or absent. Security posture is basic with no DNSSEC and no security headers detected, though HTTPS is presumed given the URL scheme. Overall, the site appears to be a parked domain rather than an active business website.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

10 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching williamsburg.org

This scan found 22 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
77
Security headers
25
Email security
65
DNS health
50
Network security
100
GDPR outside view
50
Average
61

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention williamsburg.org, from OffSeq Breach.

No leaked records found

Breach holds no records for williamsburg.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Due to the lack of content and business information, no clear market positioning, business model, or target audience can be identified. The domain is likely held for future use or resale, as indicated by Afternic name servers and parking scripts. There are no visible partnerships, subsidiaries, or certifications. The absence of contact details and policies suggests no active commercial operations at this URL. The business intelligence is limited to domain registration data and parking status.

Security posture

The security posture is minimal. The domain uses clientTransferProhibited status to prevent unauthorized transfers, which is positive. However, DNSSEC is not enabled, and no security headers such as Content-Security-Policy or X-Frame-Options are present, increasing risk exposure. No forms or inputs are present, reducing attack surface but also indicating no user interaction. No incident response or vulnerability disclosure information is available. Overall, the site has a low security maturity level and would benefit from basic security enhancements if developed further.

Recommendations

  1. Enable DNSSEC to improve domain name system security.
  2. Implement standard security headers to protect against common web attacks.
  3. Add privacy and cookie policies to comply with GDPR and other regulations.
  4. Provide clear contact information and business details to improve trust and credibility.
  5. If the site is to be developed, adopt modern CMS and frameworks with secure coding practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal and appears to be a parking or placeholder page.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms present.
  4. Only external scripts are from Google Adsense and wsimg.com for parking-lander functionality.
  5. No security headers detected and DNSSEC is not enabled.
  6. Domain is old and registered with a reputable registrar but uses Afternic name servers indicating parking.
  7. No business or branding information visible on the page.
  8. No analytics or tracking services detected beyond Adsense.
  9. No social media or external business links found.
Technical notes

Notes

The site uses a minimal technical stack with JavaScript and CSS assets loaded from wsimg.com and Google Adsense scripts for advertising. No CMS or frameworks are detected. The site is mobile responsive at a basic level but lacks SEO meta tags and accessibility features. Hosting provider is not explicitly identified but likely related to wsimg.com infrastructure. Performance is moderate given minimal content. The domain uses Afternic name servers, indicating domain parking or resale status. There is no evidence of technical debt but also no advanced technical implementation.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with williamsburg.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review williamsburg.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.