Skip to main content

Security report for ej.uz

Technology · Latvia

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

78/100

Risk levelLow

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

ej.uz is a Latvian-based URL shortening service offering users the ability to create short and custom URLs for use across social media and advertising materials. The website is well-branded, localized in Latvian, and targets Latvian internet users seeking a reliable link shortening solution. The service emphasizes safety and ease of use, with a simple form for URL shortening and options for custom short links. The site includes social media integration and a cookie consent mechanism, reflecting awareness of privacy regulations. Technically, the site uses modern web standards with HTML5, CSS3, and JavaScript, and is served over HTTPS with a CSRF token implemented, indicating basic security hygiene. However, no advanced security headers or explicit security policies are published. The absence of direct contact emails or phone numbers limits direct communication channels, relying instead on a contact form and Facebook Messenger link. Overall, the site is functional, secure at a basic level, and compliant with privacy norms, but could improve transparency and security posture by publishing terms of service, security policies, and vulnerability disclosure information.

Scanned

This is an earlier scan of ej.uz. View the latest report

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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

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

    • 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

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching ej.uz

This scan found 18 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
52
Security headers
95
Email security
80
DNS health
75
Network security
100
GDPR outside view
68
Average
78

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

ej.uz operates in the technology sector as a small-sized URL shortening service primarily serving the Latvian market. Its business model revolves around providing free or possibly supported URL shortening with custom alias options. The service leverages social media channels for user engagement and support, including Twitter, Facebook Messenger, and GitHub sponsorship. The mention of a related domain, sald.us, suggests a possible ecosystem or sister service. The company does not publicly disclose detailed business registration or legal information, which is common for small tech startups or individual operators. The website's clean design, localized content, and clear value proposition position it well within its niche, though growth and trust could be enhanced by adding more comprehensive business and legal disclosures.

Security posture

The website demonstrates a moderate security posture with HTTPS enforced and CSRF protection implemented on forms. However, it lacks several recommended security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which could mitigate common web vulnerabilities. No explicit security or incident response policies are published, and no vulnerability disclosure or security.txt files are present. The absence of direct contact emails for security incidents limits incident response readiness. No known vulnerabilities or exposed sensitive data were detected in the provided content. Overall, the security posture is adequate for a small web service but would benefit from enhanced security headers, published policies, and clearer incident response channels.

Recommendations

  1. Implement and publish a comprehensive security policy and incident response contact information.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish terms of service to clarify user rights and responsibilities.
  4. Introduce a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance contact options by providing verified company emails or phone numbers for support and security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Populārākais garu tīmekļa saišu īsināšanas serviss Latvijā. Droši izmanto ej.uz īssaites Twitter, Facebook, reklāmas materiālos, gan drukā, gan tiešsaistē!
Key services
URL shortening, Custom short URLs
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • CSRF token present
  • Input validation on URL fields

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a Latvian URL shortening service with clear branding and localized content
  2. No direct contact emails or phone numbers found; contact primarily via form and Facebook Messenger
  3. No explicit terms of service or security policy published
  4. Cookie consent banner present and functional
  5. No analytics or advertising scripts detected in provided HTML
  6. Good HTTPS and CSRF token usage indicates basic security hygiene
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS3, and JavaScript, with no detected use of major CMS or frameworks. The presence of a CSRF token indicates some backend security considerations. The site is mobile-optimized with responsive design elements and includes meta tags for SEO and social media sharing (Open Graph and Twitter Cards). Performance is likely fast given the minimalistic design and absence of heavy external scripts. Accessibility is basic but present, with form labels and alt text for images. There is no evidence of analytics or tracking scripts, which reduces privacy concerns but also limits marketing insights. Hosting provider details are not disclosed. Overall, the technical implementation is solid for a small service but could be enhanced with modern frameworks or CMS for scalability and maintainability.
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. 78/100Low28 findingsView report
Reviews of this site

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

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.