Skip to main content

Security report for francity.com

Other · N/a

Partial score · DNS & email only

75/100

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

The website francity.com is currently inaccessible due to a Cloudflare 523 error indicating that the origin web server is unreachable. This prevents any meaningful content or business information from being accessed or analyzed. The domain is registered with GoDaddy since 2014 and uses Cloudflare DNS servers, but DNSSEC is not enabled. No privacy, cookie, or terms of service policies are present, nor is there any contact information or business details visible on the error page. The technical infrastructure relies on Cloudflare as a CDN and security provider, but the origin server misconfiguration or downtime severely impacts availability and trust. From a security perspective, the site lacks visible security headers and does not provide any incident response or security policy information. The absence of DNSSEC and the current origin server unreachability are significant concerns. No analytics, advertising, or tracking technologies are detected, indicating minimal digital footprint beyond Cloudflare's protection layer. Overall, the website's risk profile is elevated due to unavailability and lack of transparency. The domain registration appears legitimate and consistent with a business domain age, but the lack of accessible content and security best practices reduces confidence. Strategic remediation should focus on restoring origin server availability, enabling DNSSEC, and publishing essential compliance and contact information to improve trust and security posture.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

1 finding rated critical or high. Fix these first.

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

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching francity.com

This scan found 11 issues across 4 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
70
DNS health
75
Network security
100
Average
80
After the cap
75

Not counted

  • Security headers: did not complete in this scan.
  • GDPR outside view: 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

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 website being inaccessible, no direct business intelligence can be extracted from the site content. The domain age suggests a potentially established entity since 2014, but no company name, services, or market positioning are available. The use of Cloudflare and GoDaddy indicates standard hosting and CDN choices. Without accessible content, insights into revenue streams, customer segments, or partnerships cannot be determined. The lack of contact or policy pages further limits business intelligence extraction.

Security posture

The current security posture is weak due to the origin server being unreachable, resulting in a Cloudflare 523 error. This indicates potential DNS misconfiguration or server downtime. No security headers or SSL/TLS configuration details are visible. The absence of privacy and cookie policies, incident response contacts, and vulnerability disclosure mechanisms highlights compliance gaps. DNSSEC is not enabled, reducing domain security. Overall, the site lacks visible security best practices and readiness for incident response, increasing operational risk.

Recommendations

  1. Restore origin server availability and verify DNS A record settings to resolve Cloudflare 523 error.
  2. Enable DNSSEC to enhance domain name system security and prevent spoofing.
  3. Implement and publish privacy and cookie policies to improve compliance and user trust.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Establish and disclose incident response contacts and vulnerability disclosure procedures.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. The website is showing a Cloudflare 523 error page indicating the origin server is unreachable, blocking access to actual content. 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
poor
Accessibility
poor
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 content is inaccessible due to Cloudflare 523 error indicating origin server is unreachable.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or business details available on the page.
  4. No forms or data collection mechanisms detected.
  5. Minimal HTML content focused on error messaging.
  6. No SEO or accessibility features detected.
  7. No analytics or advertising scripts detected.
  8. Domain is registered and active but website is currently down or misconfigured.
Technical notes

Notes

The website uses Cloudflare as a CDN and DNS provider with GoDaddy as the registrar. The domain is protected with clientDeleteProhibited and related EPP statuses but lacks DNSSEC. The HTML content is minimal and serves only as an error page with no meta tags beyond basic charset and viewport. No CMS or frameworks are detected. Performance is poor due to unavailability. Mobile optimization and accessibility are minimal given the error page nature. No analytics or marketing scripts are present. The technical debt includes lack of DNSSEC, missing security headers, and origin server misconfiguration causing downtime.
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 francity.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 francity.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.