Skip to main content

Security report for arche-tickets.de

Other · N/a

High risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

46/100

Risk levelHigh

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

The website arche-tickets.de is currently inaccessible, returning a 403 Forbidden error page indicating that access is blocked by server permissions. Due to this, no meaningful content, metadata, or business information is available for analysis. The technical infrastructure is based on Apache 2.4.58 running on Windows with OpenSSL 3.1.3 and PHP 8.2.12, hosted likely via domaindiscount24.net nameservers. No CMS or frameworks are detected. Security posture is minimal with no security headers observed and only basic SSL configuration implied by HTTPS on port 443. The WHOIS data shows the domain is active with standard registrar nameservers but lacks detailed registrant information. Overall, the site lacks transparency, content, and compliance indicators, resulting in a low trust and security score.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

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

  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 arche-tickets.de

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
77
Security headers
15
Email security
60
DNS health
60
Network security
40
GDPR outside view
25
Average
46

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 arche-tickets.de, from OffSeq Breach.

Total records
2
Employees
0
Customers
2
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for arche-tickets.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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 accessible content and metadata, no business intelligence insights can be derived. The domain appears to be related to ticketing services based on the domain name, but no explicit business model, market positioning, or services are presented. No contact details, policies, or certifications are available to support credibility or operational insights.

Security posture

The security posture is weak as the site is inaccessible and does not present any security policies, incident response contacts, or vulnerability disclosures. The absence of security headers and the presence of a 403 Forbidden error without clear explanation may indicate misconfiguration or overly restrictive server settings. No WAF vendor is detected, and no advanced security mechanisms are evident. Compliance with GDPR or other frameworks cannot be confirmed.

Recommendations

  1. Resolve the 403 Forbidden error to allow legitimate user access to the website content.
  2. Publish comprehensive privacy and cookie policies to comply with GDPR and improve user trust.
  3. Add clear contact information including emails and phone numbers for customer support and incident response.
  4. Implement standard security headers and improve SSL/TLS configuration to enhance security posture.
  5. Consider deploying a recognized WAF solution with proper configuration to protect the site without blocking legitimate users.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error indicating access is blocked by server permissions. No specific WAF vendor detected. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Apache/2.4.58, OpenSSL/3.1.3, PHP/8.2.12
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 metadata, structured data, or business information found in HTML.
  3. No contact information, policies, or forms detected.
  4. Technical stack includes Apache, OpenSSL, and PHP versions indicating a Windows hosting environment.
  5. No external links or social media references found.
  6. No security headers detected in the provided data.
  7. Domain WHOIS data is minimal but consistent with active registration.
  8. No evidence of WAF challenge page such as Cloudflare or Sucuri.
  9. Content safety is rated safe due to lack of content.
  10. Overall website quality and trustworthiness are low due to lack of accessible content.
Technical notes

Notes

The website runs on Apache 2.4.58 with PHP 8.2.12 on a Windows server environment, using OpenSSL 3.1.3 for SSL/TLS. The domain uses nameservers from domaindiscount24.net, indicating a common hosting provider or registrar service. No CMS or JavaScript frameworks are detected. The site currently serves only a 403 Forbidden error page with minimal HTML content and no metadata or SEO tags. Performance, mobile optimization, and accessibility cannot be assessed due to lack of content. The technical setup suggests a basic hosting environment but with misconfigured access controls preventing content delivery.
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 arche-tickets.de. 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 arche-tickets.de.

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.