Skip to main content

Security report for staffburg.com

Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

38/100

Risk levelHigh

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

The website staffburg.com currently presents no accessible content or metadata, rendering it effectively a blank site. There is no visible business information, contact details, or user-facing content. The domain is registered and hosted on fidoman.ru infrastructure but lacks a valid SSL certificate, resulting in no HTTPS support and a poor security posture. The absence of privacy policies, cookie banners, or terms of service further indicates a lack of compliance with common data protection regulations. Overall, the site is not professionally maintained and does not provide any meaningful information to visitors or customers. From a technical perspective, the site is minimal with only two resources loaded and a very small page size, but it suffers from slow load times and no modern web technologies or frameworks detected. The lack of security headers, DNSSEC, and other best practices exposes the site to potential risks. No analytics or advertising technologies are present, indicating minimal digital marketing or user tracking. Security-wise, the absence of HTTPS is a critical vulnerability, severely impacting trust and data protection. No incident response or security policies are found, and no certifications or vulnerability disclosures are available. The WHOIS data is consistent but provides limited insight due to lack of business information on the site. Given these findings, the overall risk level is high due to poor security posture, lack of content, and absence of compliance measures. Strategic recommendations include immediate implementation of HTTPS, development of meaningful website content, and establishment of privacy and security policies to improve trust and compliance.

Scanned

NIS2 and GDPR posture

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

8 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 staffburg.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
0
Security headers
15
Email security
70
DNS health
85
Network security
40
GDPR outside view
15
Average
38

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 intelligence available from the website content or metadata. The domain is registered and hosted on fidoman.ru, but no company name, description, or sector information is provided. No contact details or social media presence is evident. The lack of content and policies suggests the site is either under development or abandoned. No competitive positioning, revenue models, or customer targeting can be inferred. The absence of partnerships or related domains further limits business insights.

Security posture

The security posture of staffburg.com is poor. The site lacks a valid SSL certificate and does not support HTTPS, exposing users to interception risks. No security headers or DNSSEC are configured, and no vulnerability disclosures or incident response contacts are published. The absence of privacy and cookie policies indicates non-compliance with GDPR and other regulations. No evidence of secure coding practices or monitoring is present. These deficiencies pose significant risks to data confidentiality and integrity.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS and secure user connections.
  2. Develop and publish comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  4. Add DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  5. Create meaningful website content including business information, contact details, and terms of service to improve professionalism and credibility.
Technical notes

Notes

The website is hosted on a single IPv4 address (195.209.35.54) with DNS and mail services managed by fidoman.ru. No SSL certificate is installed, and no modern TLS protocols are supported. The site loads only two resources totaling 196 bytes with a slow load time of 4734 ms, indicating poor performance optimization. No CMS, frameworks, or analytics tools are detected. The HTML content is empty, lacking metadata, scripts, or structured data. The absence of security headers and DNSSEC further highlights technical weaknesses. Overall, the infrastructure is minimal and requires modernization and security enhancements.
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 staffburg.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 staffburg.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.