Skip to main content

Security report for rtlcss.com

Mohammad Younes · Technology · N/a

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

Security score

55/100

Risk levelMedium

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

RTLCSS is a specialized open source framework designed to convert CSS stylesheets from Left-To-Right (LTR) to Right-To-Left (RTL) layouts, targeting web developers and designers who require RTL support. The website presents a focused technical offering with an online playground and CDN services, positioning itself as a niche tool in the web development ecosystem. The business is small, founded in 2013, and maintained by Mohammad Younes, with a consistent domain registration history and active GitHub presence. Technically, the site uses a modern static site generator (Hexo), standard web technologies, and integrates common libraries such as jQuery and Font Awesome. Performance and mobile optimization are adequate, though accessibility is basic. Security posture is moderate with HTTPS enabled but lacks security headers and formal policies. Advertising is present via Carbon Ads and Google Adsense, with moderate user tracking through Google Analytics. Privacy and cookie policies are absent, and no contact information or security incident response details are provided, which impacts compliance and trust. Overall, the site is professional and functional but could improve in privacy, security, and transparency aspects.

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

10 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 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';…

  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

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

Keep watching rtlcss.com

This scan found 28 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
62
Security headers
15
Email security
40
DNS health
75
Network security
100
GDPR outside view
35
Average
55

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

RTLCSS operates in the technology sector, providing a unique CSS transformation service that automates RTL stylesheet generation, reducing developer effort. Its business model revolves around open source software with supplementary online tools and CDN hosting. The project benefits from a clear market niche with limited direct competition, leveraging GitHub for community engagement and issue tracking. The target audience includes front-end developers and organizations needing RTL support for multilingual websites. Revenue streams likely include donations, sponsorships, or indirect monetization via advertising. Partnerships with GitHub and affiliations with related projects like AlertifyJS and isResponsive enhance its ecosystem. Growth indicators include active repository maintenance and social media presence. Strategic observations suggest opportunities to expand compliance, security, and user trust to broaden adoption.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain transfer protection enabled. However, it lacks critical security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate common web attacks. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other regulations. The absence of a security.txt file or vulnerability disclosure policy reduces transparency and incident response readiness. No exposed sensitive data or vulnerable libraries were detected in the HTML content. Advertising scripts and third-party integrations introduce moderate tracking and potential privacy concerns. Overall, the security posture is functional but requires enhancements in policy documentation, header implementation, and incident response mechanisms to meet higher compliance and security standards.

Recommendations

  1. Implement comprehensive privacy and cookie policies with explicit user consent mechanisms to improve GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to enhance protection against common web vulnerabilities.
  3. Publish a security.txt file and establish a clear vulnerability disclosure process to improve incident response readiness and transparency.
  4. Provide clear contact information including security and support emails to enhance trust and facilitate communication.
  5. Enable DNSSEC for the domain to strengthen DNS security and prevent spoofing attacks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mohammad Younes
Description
RTLCSS is a framework for transforming Cascading Style Sheets (CSS) from Left-To-Right (LTR) to Right-To-Left (RTL).
Key services
CSS transformation from LTR to RTL, Online playground for CSS conversion, CDN hosting for RTLCSS
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery, Font Awesome, AlertifyJS, Normalize.css
Frameworks
Hexo (static site generator)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of clientTransferProhibited domain status

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
Carbon Ads, Google Adsense
Tracking pixels
Google Adsense tracking
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a niche technical tool for CSS RTL conversion
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly listed
  4. Uses multiple external libraries and CDNs
  5. Includes advertising via Carbon Ads and Google Adsense
  6. Good use of social media and GitHub integration
  7. No security.txt or vulnerability disclosure information
  8. No security headers detected in HTML content
  9. Domain WHOIS data is consistent and stable
Technical notes

Notes

The website is built using Hexo, a static site generator, delivering fast and stable content with modern HTML5, CSS3, and JavaScript technologies. It leverages popular libraries such as jQuery, Font Awesome, and AlertifyJS for UI and functionality. External resources are loaded from reputable CDNs, improving performance and reliability. The site includes Google Analytics and Google Adsense scripts for tracking and monetization. Mobile optimization is good, but accessibility features are basic and could be improved. The site lacks advanced SEO structured data like JSON-LD but includes Open Graph metadata for social sharing. No CMS beyond Hexo is detected. Hosting appears to be managed via NameCheap DNS services. Overall, the technical infrastructure is solid for a small open source project but could benefit from enhanced accessibility and SEO improvements.
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 rtlcss.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 rtlcss.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.