Skip to main content

Security report for filesor.com

Other · N/a

Partial score · DNS & email only

68/100

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

The website filesor.com is currently inaccessible due to a Cloudflare error 521 indicating the web server is down. The domain is registered since 2010 with NameCheap, Inc. and uses Cloudflare DNS services. No business, contact, or policy information is available on the site, and the content is limited to an error page. The technical infrastructure relies on Cloudflare for CDN and security, but the origin server is not responding, causing service disruption. Security posture is weak due to lack of visible security headers and no SSL configuration details. Privacy compliance and business credibility cannot be verified due to lack of content. Overall, the site is currently non-functional and provides no user or business information.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
6of 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

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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching filesor.com

This scan found 17 issues across 5 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
75
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
68

Not counted

  • Security headers: did not complete in this scan.
  • 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 filesor.com, from OffSeq Breach.

Total records
221
Employees
0
Customers
158
Third parties
63
Weak passwords
27%

4 subdomains 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 filesor.com.

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 absence of business content, no detailed business intelligence can be derived. The domain age suggests a potentially established entity, but no information about market positioning, services, or partnerships is available. The site does not display any trust indicators or certifications. The lack of contact information and policies limits assessment of business credibility and compliance.

Security posture

The security posture is minimal with reliance on Cloudflare for edge security. The origin server is down, causing a critical availability issue. No security headers or incident response information is present. DNSSEC is not enabled, which could improve DNS security. No vulnerability disclosure or security policies are found. The site lacks privacy and cookie policies, indicating poor compliance readiness.

Recommendations

  1. Restore origin web server availability to resolve the 521 error and restore service.
  2. Enable DNSSEC to enhance DNS security and trust.
  3. Implement and publish privacy, cookie, and security policies to improve compliance.
  4. Add security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  5. Establish incident response contacts and vulnerability disclosure mechanisms publicly.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare error 521 page indicating web server is down and content is blocked. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare
Performance
slow
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
10/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 is currently inaccessible due to web server down (Error 521).
  2. Content is minimal and consists solely of a Cloudflare error page.
  3. No business or contact information is present on the page.
  4. No privacy, cookie, or terms of service policies found.
  5. No forms or data collection mechanisms detected.
  6. No analytics or advertising scripts detected.
  7. No social media or external business-related links except Cloudflare.
  8. No security headers or SSL configuration details available from content.
  9. WHOIS data is publicly available and consistent with a legitimate domain.
  10. Website content and metadata are insufficient for full analysis.
Technical notes

Notes

The website uses Cloudflare as a CDN and DNS provider but the origin server is currently unreachable, resulting in a 521 error. No CMS or frameworks are detected from the HTML content. The site lacks meta tags beyond basic charset and viewport. No analytics or tracking scripts are present. Performance and SEO are poor due to lack of content and error state. Mobile optimization is basic as the page is minimal. Accessibility features cannot be assessed due to limited content.
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

Earlier scans of this domain

  1. 68/100Medium26 findings · partial scanView report
Reviews of this site

Share your experience with filesor.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 filesor.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.