Skip to main content

Security report for stjhlibya.com

Other · N/a

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

Security score

53/100

Risk levelMedium

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

The website stjhlibya.com is currently inaccessible due to a DNS resolution error as indicated by the Cloudflare error page. This prevents any meaningful content or business information from being accessed or analyzed. The site appears to be either misconfigured or not yet fully set up on Cloudflare's network. There is no visible business description, contact information, or security and privacy policies available. The technical infrastructure is limited to Cloudflare's error handling scripts and styles, with no CMS or other technologies detected. Security posture is poor due to lack of HTTPS and security headers, and the site is effectively blocked from public access. Overall, the site is non-operational in its current state, resulting in a very low trust and credibility score.

Scanned

NIS2 and GDPR posture

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

    • 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

  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 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 stjhlibya.com

This scan found 19 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
35
Email security
85
DNS health
85
Network security
100
GDPR outside view
10
Average
53

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 stjhlibya.com, from OffSeq Breach.

Total records
12
Employees
2
Customers
4
Third parties
6
Weak passwords
8%

Latest record dated 2025-07-03 · 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 stjhlibya.com.

Select it in the checkout above.

Masked preview

  • –mail.stjhlibya.com2025-07-03
  • –mail.stjhlibya.com2025-04-15

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

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

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 DNS resolution failure and lack of accessible content, no business intelligence can be derived. There are no indications of market positioning, business model, or services. No partnerships or subsidiaries are identifiable. The domain's WHOIS data was not provided, preventing further legitimacy or registration analysis.

Security posture

The security posture is critically weak as the site is inaccessible and does not present any security headers or HTTPS configuration. The DNS failure itself is a critical operational vulnerability. No incident response or vulnerability disclosure information is available. The site does not comply with privacy regulations as no policies are present. The use of Cloudflare indicates some level of intended security, but the current configuration prevents normal operation.

Recommendations

  1. Resolve DNS configuration issues immediately to restore website accessibility.
  2. Ensure HTTPS is properly configured with valid SSL/TLS certificates.
  3. Implement standard security headers to improve security posture.
  4. Publish privacy, cookie, and terms of service policies to comply with regulations.
  5. Add clear contact and incident response information to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. The page is a Cloudflare DNS resolution error page indicating the domain stjhlibya.com is not resolvable currently. Content is blocked due to DNS failure. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
Cloudflare, JavaScript
Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Analytics and tracking

Services
Cloudflare Radar
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 DNS resolution error.
  2. Content is a Cloudflare error page with no business or contact information.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or forms present.
  5. No security headers or SSL information available.
  6. External links only to Cloudflare domains related to error reporting and performance.
  7. No social media or business-related external links detected.
  8. No structured data or metadata beyond basic error page tags.
  9. Website appears to be non-operational or misconfigured.
Technical notes

Notes

The website is currently serving only a Cloudflare DNS error page with minimal HTML and JavaScript related to error feedback and performance monitoring. No CMS or other platform technologies are detected. The site lacks mobile optimization, accessibility features, and SEO metadata. The hosting provider is Cloudflare, but the domain DNS is not resolving, indicating a critical infrastructure issue. Performance cannot be assessed due to lack of content. Technical debt is high as the site is non-functional.
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 stjhlibya.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 stjhlibya.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.