Skip to main content

Security report for stilyoapps.com

Other · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

69/100

Risk levelMedium

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

The website at stilyoapps.com is currently inaccessible, returning a 403 Forbidden error page served by nginx. This prevents any meaningful content or metadata extraction, resulting in a lack of visible business information, policies, or contact details. The domain is registered with GoDaddy.com, LLC since 2018 and uses Amazon AWS DNS servers, indicating a legitimate registration and hosting setup. However, the absence of accessible content and security headers limits the ability to assess the website's technical maturity and security posture. The security posture is weak due to lack of visible HTTPS enforcement and security best practices. Overall, the site appears blocked or restricted, which significantly reduces trust and usability.

Scanned

NIS2 and GDPR posture

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

7 findings rated critical or high. Fix these first.

  1. 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 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';…

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching stilyoapps.com

This scan found 22 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
77
Security headers
40
Email security
70
DNS health
85
Network security
100
GDPR outside view
40
Average
69

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

Total records
61
Employees
6
Customers
39
Third parties
16
Weak passwords
13%

Latest record dated 2026-01-10 · 5 subdomains 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 stilyoapps.com.

Select it in the checkout above.

Masked preview

  • –stilyoapps.com2026-01-10
  • –reconvert-stage.stilyoapps.com2025-12-05
  • –stilyoapps.com2025-12-05
  • –demo.stilyoapps.com2025-09-19
  • –test-php.stilyoapps.com2025-07-25

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 lack of accessible content, no detailed business intelligence can be derived. The domain age and registrar suggest a legitimate business presence since 2018, but no information about market positioning, services, or partnerships is available. No contact or social media information is present to assess customer engagement or support infrastructure.

Security posture

The security posture is currently poor as the website is inaccessible and does not present any security headers or visible SSL configuration. The domain status includes standard registrar locks, which is positive. DNSSEC is not enabled, representing a minor security gap. No incident response or vulnerability disclosure information is available. The site is effectively blocked, which may be intentional for security or maintenance reasons but limits transparency and trust.

Recommendations

  1. Restore website accessibility by resolving the 403 Forbidden error to allow content delivery.
  2. Implement HTTPS with a valid SSL certificate and enable DNSSEC for improved domain security.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Publish clear contact information including emails and phone numbers for customer and security incident reporting.
  5. Deploy standard security headers and conduct a security audit to identify and remediate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with minimal HTML content served by nginx, indicating access is blocked or restricted. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

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 403 Forbidden error.
  2. No metadata, scripts, forms, or external links found in the HTML content.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or social media links available.
  5. Domain is registered and active with no privacy protection but DNSSEC is not enabled.
  6. Hosting appears to be on Amazon AWS based on DNS nameservers.
  7. No security headers or SSL configuration details available from provided data.
  8. Website is effectively blocked or restricted, preventing full analysis.
Technical notes

Notes

The website is hosted on Amazon AWS infrastructure as indicated by DNS nameservers. No CMS or frameworks could be detected due to lack of content. The site returns a 403 Forbidden error with minimal HTML, indicating server-side access restrictions or misconfiguration. No scripts, meta tags, or SEO elements are present. Performance, mobile optimization, and accessibility cannot be assessed. The domain registration is consistent and stable but technical implementation is currently insufficient for a public-facing website.
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 stilyoapps.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 stilyoapps.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.