Skip to main content

Security report for apo.com

apo.com · Healthcare · Germany

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

apo.com is an established German online pharmacy specializing in medications and services for chronically ill patients. The website offers consultation, e-prescription processing, and shipping pharmacy services, positioning itself as a key player in the German healthcare e-commerce market. The site is well-branded, professionally designed, and targets a German-speaking audience with a focus on healthcare and wellness products. Technically, the site employs modern technologies such as Algolia for search and recommendations, Google Tag Manager for analytics, and Dynamic Yield for personalization, indicating a mature digital infrastructure. Security posture is strong with HTTPS enforced and no visible sensitive data exposure, though security headers and explicit privacy policies are lacking. The absence of WHOIS data for the domain is a notable anomaly, potentially indicating privacy protection or registry restrictions, which slightly impacts trustworthiness. Overall, the site is professional, secure, and user-friendly, but would benefit from enhanced privacy compliance and transparency.

Scanned

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

4 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 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 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 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

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

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. 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
75
Security headers
35
Email security
75
DNS health
85
Network security
100
GDPR outside view
68
Average
73

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

Total records
963
Employees
0
Customers
939
Third parties
24
Weak passwords
14%

9 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 apo.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Brand lookalikes

Add-on

Domains that imitate apo.com and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
92
Registered
92
Resolving
92
High or critical
0

Last checked 2026-06-20

Masked preview

  • ep•••.comMediumbitsquatting
  • ap•••.comMediumbitsquatting
  • ax•••.comMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of apo.com with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

apo.com operates in the healthcare and e-commerce sectors, focusing on pharmaceutical products and services for chronic patients. Its business model revolves around online sales, consultation, and e-prescription fulfillment. The company leverages advanced search and recommendation technologies to enhance user experience and drive sales. The presence of social media links and structured data suggests active marketing and SEO efforts. The lack of visible contact information and WHOIS details may indicate privacy considerations or registry policies. The site appears to serve a large customer base in Germany, with a comprehensive product catalog and service offerings. Strategic partnerships or subsidiaries are not evident from the data provided.

Security posture

The website demonstrates a solid security foundation with HTTPS enabled and no exposed sensitive information in the HTML content. Use of reputable third-party libraries and analytics tools is observed. However, the absence of key security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options reduces the overall security posture. No vulnerability disclosures or incident response contacts are published, which could hinder rapid response to security incidents. Privacy compliance is partial, with no explicit privacy or cookie policies detected, potentially exposing the company to regulatory risks under GDPR. The domain's missing WHOIS data raises questions about registration transparency but does not directly indicate compromise. Overall, the security posture is good but can be improved with enhanced headers, policies, and transparency.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance and consent mechanisms.
  2. Add and configure security headers including CSP, HSTS, and X-Frame-Options to strengthen defense against common web attacks.
  3. Publish a security policy and incident response contact information to improve transparency and readiness.
  4. Consider adding a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features to meet compliance standards and improve user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
apo.com
Description
Medikamente & Services für chronisch Kranke ✚ Beratung, E-Rezept & Versandapotheke ⚕ ♡ apo.com
Key services
Medication sales, Consultation services, E-prescription processing, Shipping pharmacy services
Content quality
good
Branding
consistent

Technology

Stack
Algolia Search, Algolia Recommend, Google Tag Manager, Dynamic Yield, Font Awesome 6
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of secure external libraries

Analytics and tracking

Services
Google Tag Manager, Algolia Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Dynamic Yield
Marketing tools
Algolia Recommend, Algolia Search
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content in German language
  2. Strong focus on healthcare and pharmacy services for chronic patients
  3. Use of modern search and recommendation technologies (Algolia)
  4. No explicit privacy or cookie policy pages detected in provided content
  5. No visible contact emails or phone numbers in the HTML snippet
  6. No security.txt or vulnerability disclosure information found
  7. No WHOIS data available, which is unusual for a .com domain
  8. Website uses HTTPS and includes structured data for SEO
  9. No adult or NSFW content detected
Technical notes

Notes

The website uses a modern tech stack including Algolia for search and recommendations, Google Tag Manager for analytics, and Dynamic Yield for personalization. The HTML structure is valid and includes SEO-friendly metadata and structured data (JSON-LD) for organization and website schema. Performance is moderate with asynchronous loading of scripts and use of CDN-hosted libraries. Mobile optimization is good, with responsive design elements and accessible navigation. However, no CMS or hosting provider information is explicitly detected. The site could benefit from improved accessibility features and additional security headers. Overall, the technical implementation supports a robust e-commerce platform with room for incremental 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 apo.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 apo.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.