Skip to main content

Security report for iauto.lv

iAuto.lv · Media · Latvia

High risk. 8 critical or high findings in GDPR outside view and Security headers.

Security score

45/100

Risk levelHigh

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

iAuto.lv is a Latvian automotive news portal providing a wide range of content including automotive news, sports, forums, classifieds, and user-generated content. The site targets Latvian-speaking automotive enthusiasts and general audiences interested in vehicles and related topics. It operates primarily as an advertising-supported media platform with additional services such as classifieds and insurance calculators. Technically, the site uses a custom or unknown CMS with technologies including nginx, jQuery, Font Awesome, Google Tag Manager, and Gemius analytics. Hosting is supported by Cloudflare DNS and a dedicated IP. However, the site lacks a valid SSL/TLS certificate and does not support modern TLS protocols, which significantly impacts its security posture. Cookie consent mechanisms are implemented, supporting GDPR compliance to a basic degree. The absence of explicit contact information and security policies reduces business credibility somewhat. Overall, the site is functional with good content quality but requires urgent security improvements to protect users and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
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

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

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

Keep watching iauto.lv

This scan found 20 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
75
Security headers
35
Email security
50
DNS health
70
Network security
40
GDPR outside view
0
Average
45

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

The website holds a solid position in the Latvian automotive media market, offering news, forums, and classifieds that attract a medium-sized audience. Its business model relies on advertising revenue and partnerships with related domains such as zip.lv for classifieds and insurance services. The site maintains active social media profiles across major platforms, enhancing its reach and engagement. While content is regularly updated and relevant, the lack of visible company contact details and security certifications may limit trust from more security-conscious users. The partnership ecosystem includes related domains for classifieds and insurance, indicating a diversified service offering. Growth potential exists if security and compliance gaps are addressed.

Security posture

The current security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential interception and data tampering risks. Security headers such as XSS protection and content-type options are present, but critical features like HSTS, OCSP stapling, and session resumption are missing. No vulnerability disclosure or incident response policies are publicly available. Cookie consent is implemented, but overall privacy compliance is basic. The site should prioritize obtaining and configuring a valid SSL certificate, enabling modern TLS protocols, and enhancing security headers to improve protection and user trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Add a security.txt file to facilitate vulnerability reporting and improve transparency.
  5. Publish clear contact information including security and incident response contacts.
  6. Regularly audit and update third-party scripts and libraries to avoid vulnerabilities.
  7. Enhance privacy policy and cookie consent mechanisms to fully comply with GDPR requirements.
  8. Improve mobile optimization and accessibility features for better user experience.
  9. Monitor and secure DNS settings, including enabling DNSSEC and domain protection locks.
Technical notes

Notes

The website runs on nginx with a custom or unknown CMS, utilizing jQuery 1.12.4 and Font Awesome 6.2.0 for frontend components. Google Tag Manager and Gemius provide analytics and tracking capabilities. Advertising is managed via OpenX ad server scripts. DNS is managed through Cloudflare nameservers, but DNSSEC is not enabled. Performance metrics are missing or zero, indicating potential issues with load time measurement or slow loading. Mobile optimization is basic with responsive design elements. The lack of HTTPS and modern TLS protocols is a critical technical deficiency. The site uses cookie consent scripts with localStorage and cookie fallbacks for user preferences. Overall, the technical infrastructure is functional but outdated in security and performance aspects, requiring modernization and security hardening.
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 iauto.lv. 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 iauto.lv.

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.