Skip to main content

Security report for tripcheck.com

Oregon Department of Transportation · Transportation · United States

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

59/100

Risk levelMedium

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

TripCheck is an official Oregon Department of Transportation website providing comprehensive traveler information including road conditions, weather forecasts, traffic cameras, and commercial vehicle restrictions. The site serves as a critical resource for travelers and commercial operators within Oregon, offering real-time data and various travel-related services. The business model is government-operated, focusing on public service and transportation safety. The website is well-branded and consistent with state government standards, targeting a broad audience of Oregon travelers and transport professionals. Technically, the site employs modern JavaScript frameworks such as Dojo Toolkit and jQuery, along with Esri's ArcGIS API for mapping functionalities. The infrastructure appears to be hosted on state government servers, ensuring reliability and alignment with public sector standards. The site is moderately optimized for performance and mobile devices, with good SEO practices and basic accessibility features. From a security perspective, the domain is well-protected with registrar-level domain status locks, but lacks DNSSEC implementation and visible security headers. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other privacy regulations. There is no exposed sensitive data or vulnerable libraries detected, but the absence of incident response contacts and security policies reduces the overall security posture. Overall, the website is trustworthy and professional, serving its public service mission effectively. However, improvements in privacy compliance, security headers, and incident response transparency are recommended to enhance user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

9 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 tripcheck.com

This scan found 26 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. The full timeline opens with your unlock code.

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
67
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
35
Average
59

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

TripCheck holds a strong market position as the official Oregon state transportation information portal, operated by the Oregon Department of Transportation. Its competitive advantage lies in providing authoritative, real-time travel data and services tailored to Oregon travelers and commercial vehicle operators. The business model is non-commercial, focusing on public service and safety. Revenue streams are likely government-funded. The target customer segments include daily commuters, commercial truck drivers, and tourists. The partnership ecosystem includes other state DOTs and federal transportation agencies. The site demonstrates stable growth and consistent content updates, reflecting ongoing operational support and strategic alignment with state transportation goals.

Security posture

The website exhibits a moderate security maturity level with domain registration protections and no visible vulnerabilities in the codebase. However, the lack of DNSSEC, security headers, privacy policies, and incident response information indicates gaps in security best practices and compliance. There is no evidence of malware, phishing, or exposed credentials. The absence of a vulnerability disclosure policy or security.txt file limits transparency and user trust. Data protection practices are unclear due to missing privacy documentation. Incident response readiness appears minimal from public information. Overall, the security culture could be improved by adopting recognized frameworks and publishing security policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR and privacy compliance.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the website against common attacks.
  4. Publish a security policy and incident response contact information to increase transparency and user trust.
  5. Conduct an accessibility audit and improve features to meet WCAG standards for better inclusivity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Oregon Department of Transportation
Description
The TripCheck website provides roadside camera images and detailed information about Oregon road traffic congestion, incidents, weather conditions, services and commercial vehicle restrictions and registration.
Key services
Road conditions map, NOAA weather forecasts, Traffic cameras, Commercial vehicle restrictions, Travel time reports, Rest areas and Sno-Parks information, Transit and travel resources
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Dojo Toolkit, jQuery, Esri ArcGIS API, Google Fonts, FontAwesome
Frameworks
Dojo
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • Domain status includes clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, clientUpdateProhibited indicating domain protection
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected from scripts

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Google Analytics (gtag.js)
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Official Oregon Department of Transportation site providing traveler information
  2. No privacy or cookie policies found, indicating compliance gaps
  3. No contact emails or phone numbers explicitly listed on main page
  4. Use of modern JavaScript frameworks and mapping APIs
  5. No visible security policy or incident response information
  6. No forms detected that collect user data
  7. External links mostly to government or official partner sites
  8. No social media links found in main content
  9. No security headers detected in provided data
  10. Domain DNSSEC not enabled, which is a security improvement opportunity
Technical notes

Notes

The website uses a mature technology stack including Dojo Toolkit, jQuery, and Esri ArcGIS API for interactive mapping. The infrastructure is likely hosted on government servers, ensuring reliability but possibly limiting scalability. Performance is moderate with room for optimization. The site is mobile-optimized with responsive CSS. SEO is well addressed with proper meta tags and structured navigation. There is no detected CMS, suggesting a custom or government-developed platform. Technical risks include lack of DNSSEC and missing security headers, which could expose the site to DNS attacks and clickjacking. Modernization opportunities include adopting newer JavaScript frameworks and enhancing accessibility compliance.
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 tripcheck.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 tripcheck.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.