Skip to main content

Security report for omworldfinals.com

Other · N/a

High risk. 11 critical or high findings in Email security, Network security and 3 other checks.

Security score

43/100

Risk levelHigh

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

The website omworldfinals.com currently displays a 403 Forbidden error page, indicating that access to the site content is blocked or restricted. There is no accessible business or contact information, privacy or cookie policies, or any other content that would provide insight into the company's operations or services. The domain is registered with NameCheap since 2021 and hosted on SiteGround, but the lack of accessible content severely limits the ability to assess the business or technical maturity. The site uses basic HTML and CSS with Google Fonts but no advanced frameworks or analytics are detected. Security posture is weak due to missing DNSSEC and absence of security headers, although HTTPS status cannot be confirmed from the content. Overall, the site is inaccessible for meaningful analysis and presents a low trust profile.

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

11 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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

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

Keep watching omworldfinals.com

This scan found 27 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
72
Security headers
15
Email security
60
DNS health
75
Network security
0
GDPR outside view
35
Average
43

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 · found on this site
  • 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

Due to the 403 Forbidden error and absence of any business-related content, no meaningful business intelligence can be derived. The domain age suggests a relatively new or small entity, but no company name, sector, or services are disclosed. There are no visible partnerships, certifications, or trust signals. The lack of contact information and policies further reduces business credibility and transparency.

Security posture

The security posture is minimal and incomplete. The domain lacks DNSSEC, and no security headers are present in the HTML content. The site is served with a 403 Forbidden status, which may indicate intentional access restrictions or misconfiguration. No incident response or vulnerability disclosure information is available. The absence of HTTPS confirmation and security best practices lowers the security score. Overall, the site requires significant improvements in security configuration and transparency.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security.
  2. Implement and publish privacy and cookie policies to comply with GDPR and other regulations.
  3. Provide clear contact information including emails and phone numbers for business and security inquiries.
  4. Configure security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Ensure the website is accessible with proper HTTPS configuration and avoid generic 403 error pages without guidance.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error page indicating access is blocked or restricted. No WAF vendor branding detected but content is blocked. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
HTML5, CSS3, Google Fonts
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms available.
  4. No scripts or analytics detected.
  5. Minimal technical metadata present.
  6. Domain is registered and active but site is blocked.
  7. No social media or external business links found.
  8. Site hosted on SiteGround with standard name servers.
  9. No DNSSEC enabled for domain.
  10. No security headers or SSL details available from content.
Technical notes

Notes

The website uses basic HTML5 and CSS3 with Google Fonts for typography. No JavaScript libraries, frameworks, or analytics tools are detected. The hosting provider is SiteGround, as indicated by the name servers. The site is not optimized for SEO or accessibility, and mobile optimization is basic. The 403 Forbidden error page is custom styled but provides no navigation or content. The lack of metadata such as Open Graph or JSON-LD structured data limits search engine understanding and social sharing capabilities. Overall, the technical implementation is minimal and requires modernization and content restoration.
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 omworldfinals.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 omworldfinals.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.