Skip to main content

Security report for hilltosea.com

Hill to Sea Corridor · Transportation · N/a

Medium risk. 7 critical or high findings in Email security, Security headers and 1 other check.

Security score

64/100

Risk levelMedium

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

The Hill to Sea Corridor website provides informational content about a proposed 28-mile transportation route connecting multiple transit lines and regional amenities. The site targets local residents and commuters interested in regional transit development. The business model appears to be informational or advocacy-focused without commercial transactions or services. Technically, the site uses a modern JavaScript module approach, likely React or a similar framework, hosted on DigitalOcean with DNS managed by DigitalOcean nameservers. However, the site suffers from slow load times and minimal content depth. Security posture is weak, with no valid SSL certificate, no HTTPS enabled, and absence of security headers or best practices. Privacy and compliance policies are missing, and no contact or business information is provided, limiting trust and credibility. Overall, the site is accessible but lacks fundamental security and compliance features, resulting in a low security and trust score.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

  3. 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

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

Keep watching hilltosea.com

This scan found 21 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
85
Security headers
15
Email security
60
DNS health
85
Network security
100
GDPR outside view
40
Average
64

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

Technical appendix

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

Business context

Business profile

The website serves as an informational platform for a transportation corridor project, targeting a regional audience of over 2 million residents. It does not appear to operate as a commercial entity but rather as a public or advocacy resource. The lack of business contact details, certifications, or partnerships suggests a small-scale or early-stage project presence online. The use of DigitalOcean hosting and minimal analytics indicates a lean technical setup. There is no evidence of revenue streams, partnerships, or growth indicators from the site content. The site’s market positioning is unclear beyond providing awareness of the corridor project.

Security posture

The security posture is poor due to the absence of HTTPS and a valid SSL certificate, exposing visitors to potential interception risks. No security headers or HSTS policies are implemented, increasing vulnerability to common web attacks. The site does not disclose any security policies or incident response procedures, indicating low maturity in security governance. The use of Umami analytics suggests minimal user tracking but without visible privacy controls or cookie consent mechanisms, raising compliance concerns. Overall, the site is at risk of data interception and lacks transparency in privacy and security practices.

Recommendations

  1. Obtain and deploy a valid SSL certificate to enable HTTPS across the site immediately.
  2. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Develop and publish privacy and cookie policies with clear GDPR compliance statements.
  4. Add visible contact information and consider a contact form to improve trust and user engagement.
  5. Enable HSTS with includeSubDomains and preload options to enforce secure connections.
Technical notes

Notes

The website uses a modern JavaScript module system with CSS styling, likely built with a framework such as React. Hosting and DNS are managed by DigitalOcean, a reputable provider. Performance is suboptimal with a load time of over 7 seconds and a moderate number of resources. SEO metadata is present but minimal, with no structured data or JSON-LD detected. Accessibility and mobile optimization are basic, with no advanced features or ARIA roles observed. The absence of CMS or third-party platforms suggests a custom or static site build. Technical debt is indicated by missing HTTPS and security best practices, which should be prioritized to reduce operational risks.
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 hilltosea.com. 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 hilltosea.com.

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.