Skip to main content

Security report for 191j.com

Other · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

56/100

Risk levelMedium

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

The website 191j.com is currently inaccessible due to a Cloudflare Web Application Firewall (WAF) blocking page, which prevents access to any substantive content. The domain is registered since 2014 with a reputable registrar and uses Cloudflare DNS services but lacks DNSSEC. Due to the WAF block, no business information, contact details, or policies are visible, limiting the ability to assess the company's market position or services. The technical infrastructure relies on Cloudflare for security and hosting, but the lack of accessible content and metadata restricts a full digital maturity assessment. Security posture is strong in terms of attack mitigation via Cloudflare, but transparency and compliance indicators are absent. Overall, the site presents a high risk for users due to lack of accessible information and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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. 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. 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';…

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

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

Keep watching 191j.com

This scan found 26 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
37
Security headers
35
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
56

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

No business intelligence can be derived from the website content as it is blocked by Cloudflare. The domain age suggests a potentially established entity, but no visible branding, services, or contact information is available. There are no indications of market positioning, revenue streams, or partnerships. The absence of privacy and cookie policies further reduces business credibility and compliance standing.

Security posture

The website benefits from Cloudflare's security services, including clientTransferProhibited domain status and DNS hosted on Cloudflare nameservers. However, DNSSEC is not enabled, which is a missed opportunity for DNS security enhancement. The WAF blocking indicates active protection against attacks but also prevents legitimate user access. No security headers or incident response information are visible. The lack of privacy and cookie policies indicates compliance gaps. Overall, the security posture is protective but lacks transparency and user trust elements.

Recommendations

  1. Enable DNSSEC to improve DNS integrity and security.
  2. Provide accessible privacy and cookie policies to comply with GDPR and build user trust.
  3. Publish clear contact and incident response information for transparency and support.
  4. Review WAF rules to reduce false positives and allow legitimate user access.
  5. Implement security headers and ensure SSL/TLS configuration is robust and visible.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website is blocked by Cloudflare security service with a challenge page preventing 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
SEO
poor

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 WAF blocking.
  2. No visible business or contact information on the landing page.
  3. No privacy, cookie, or terms of service policies found.
  4. Domain is aged and registered with a known registrar but lacks DNSSEC.
  5. No analytics or advertising scripts detected due to blocked content.
  6. No forms or data collection mechanisms visible.
  7. No social media or external business links found except Cloudflare.
  8. Website appears to be protected against attacks but lacks transparency and user-facing content.
Technical notes

Notes

The website is protected and hosted behind Cloudflare, which provides DNS, CDN, and WAF services. The HTML content is minimal and serves only as a security block page. No CMS or additional frameworks are detectable. Performance and SEO cannot be assessed due to lack of content. Mobile optimization and accessibility cannot be evaluated. The domain registration is consistent and uses a known registrar. Technical debt cannot be assessed due to lack of content. Modernization opportunities include enabling DNSSEC and improving user-facing transparency.
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 191j.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 191j.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.