Skip to main content

Security report for ustravelinsurance.org

Other · N/a

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

Security score

65/100

Risk levelMedium

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

The website at ustravelinsurance.org/lander is currently a minimal placeholder or parking page with no substantive business content or contact information. The domain is long-established, created in 2004, and registered with a reputable registrar, Wild West Domains, LLC, but the website itself does not reflect an active or mature business presence. The site uses a parking lander system (PW) and includes Google Adsense scripts for advertising, indicating monetization attempts through ads rather than direct business services. Technically, the site uses basic JavaScript and minimal HTML with no advanced frameworks or CMS detected. Mobile optimization and SEO are basic at best, and no security headers or privacy policies are present, which negatively impacts compliance and trustworthiness. Security posture is weak due to lack of HTTPS enforcement details and missing security best practices. Overall, the site is low trust and low content quality, with no evidence of GDPR compliance or business credibility.

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

8 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 ustravelinsurance.org

This scan found 23 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
77
Security headers
25
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
65

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

There is insufficient business information on the website to determine market positioning, competitive advantages, or detailed business model insights. The domain age suggests potential for a mature business, but the current content does not support this. The presence of Google Adsense indicates a revenue stream based on advertising rather than direct service offerings. No partnerships, subsidiaries, or strategic alliances are evident from the content or linked domains. The target audience and industry classification remain unclear due to lack of descriptive content.

Security posture

The security maturity level of the website is low. No security headers were detected, and DNSSEC is not enabled on the domain, which could expose the site to DNS spoofing risks. There is no visible privacy or cookie policy, indicating non-compliance with GDPR and other privacy regulations. Incident response and vulnerability disclosure information are absent, reducing transparency and readiness for security incidents. The site does not expose sensitive data or show signs of vulnerabilities in the limited content available, but the lack of security best practices is a concern. Overall, the security posture requires significant improvement to meet modern standards.

Recommendations

  1. Enable HTTPS with a strong SSL/TLS configuration and enforce it site-wide.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and enhance user trust.
  4. Provide clear contact information and incident response channels to improve transparency and security readiness.
  5. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
JavaScript
Frameworks
PW (Lander System)
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/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 placeholder or parking page.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or business details provided on the page.
  4. Uses a parking lander system (PW) with minimal HTML content.
  5. External scripts include Google Adsense for advertising.
  6. No security headers or advanced security configurations detected.
  7. Domain is old and registered with a reputable registrar but website does not reflect active business use.
Technical notes

Notes

The website is built on a minimal technical stack primarily using JavaScript and a parking lander system (PW). It loads external scripts from Google Adsense and wsimg.com for styling and functionality. The site lacks a CMS or modern frameworks and shows basic mobile optimization. Performance is moderate given the minimal content, but SEO and accessibility are poor due to missing meta tags and content. Hosting details are limited to registrar information, with no clear hosting provider identified. The site would benefit from modernization, improved content structure, and enhanced technical SEO and accessibility features.
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 ustravelinsurance.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 ustravelinsurance.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.