Skip to main content

Security report for rtb123.com

Technology · N/a

High risk. 12 critical or high findings in Network security, Security headers and 3 other checks.

Security score

42/100

Risk levelHigh

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

The domain www.rtb123.com currently hosts a default placeholder webpage generated by Plesk, indicating that the domain is either unregistered or inactive. The website content is minimal and serves only to promote Plesk hosting control panel and related services such as Sitejet Builder and WP Guardian. There is no evidence of an active business or service operating under this domain. Technically, the site uses standard HTML5, CSS3, and JavaScript with assets hosted on Plesk's CDN. The site is mobile optimized and has basic accessibility features but lacks any advanced frameworks or CMS. Security posture is weak due to the absence of HTTPS confirmation, security headers, and privacy policies. No WHOIS registration data is available, which raises concerns about domain legitimacy and ownership. Overall, the site is not suitable for business or user engagement in its current state.

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

12 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: RDP

      Port 3389 (RDP) is publicly accessible - RDP - Remote Desktop, prime ransomware target

      What to do: Immediately restrict access to RDP using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

This scan found 24 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
72
Security headers
15
Email security
45
DNS health
85
Network security
0
GDPR outside view
35
Average
42

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 · found on this site
  • 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

The website does not represent an active business entity but rather a default hosting placeholder. There are no business details, contact information, or trust indicators. The external links direct users to Plesk and its associated services, suggesting the domain is intended for future hosting setup rather than current commercial use. There is no evidence of revenue streams, partnerships, or market positioning. The target audience implied by the placeholder content is web professionals and hosting users interested in Plesk solutions.

Security posture

The security posture is minimal. The absence of HTTPS confirmation and security headers indicates a lack of basic security best practices. No forms or data collection mechanisms are present, reducing attack surface but also indicating no active service. The lack of privacy and cookie policies suggests non-compliance with GDPR and other data protection regulations. No incident response or vulnerability disclosure information is available. Overall, the site poses low risk but also lacks any security maturity.

Recommendations

  1. Implement HTTPS with a valid SSL certificate to secure the site.
  2. Remove or replace the default placeholder page with actual business content.
  3. Add privacy and cookie policies to comply with data protection regulations.
  4. Configure security headers such as Content-Security-Policy and X-Frame-Options.
  5. Register the domain properly and provide accurate WHOIS information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
This website is a default placeholder page generated by Plesk for the domain www.rtb123.com. It provides information about Plesk hosting control panel and related services but does not represent an active business or service.
Key services
Plesk hosting control panel, Sitejet Builder (low code/no-code site builder), WP Guardian (WordPress health and security management)
Content quality
basic
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Plesk control panel, woff2 fonts
Platforms
Plesk
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
basic
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website is a default Plesk placeholder page with no active content or business presence
  2. No WHOIS registration data available for the domain
  3. No privacy, cookie, or terms of service policies found
  4. No contact information or forms present
  5. No security headers or HTTPS status available from provided data
  6. External links point to Plesk and related service domains only
  7. No analytics or tracking scripts detected
  8. No signs of adult or unsafe content
  9. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is a simple static page generated by Plesk with no CMS or advanced frameworks detected. It uses modern font formats (woff2) and standard web technologies. The hosting provider is not explicitly identified but likely Plesk or a Plesk-enabled hosting environment. Performance is moderate with no heavy scripts or resources. Mobile optimization is good due to responsive CSS. SEO optimization is basic with minimal meta tags and no structured data. There is no evidence of analytics or tracking scripts. The site is suitable as a placeholder but requires significant development for production use.
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. 43/100High29 findingsView report
Reviews of this site

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