Skip to main content

Security report for paymer.com

Цифровые чеки в криптовалюте и WebMoney · Finance · N/a

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

70/100

Risk levelMedium

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

Paymer.com operates as a digital payment platform specializing in digital checks backed by WebMoney and various cryptocurrencies. The service enables users to issue, verify, transfer, and redeem digital checks securely without requiring traditional banking or crypto wallets. The website targets individuals and merchants seeking a secure and convenient online payment method. The business model centers on facilitating digital check transactions with a focus on security and ease of use. The domain is mature, registered since 2001, indicating an established presence in the market. Technically, the website employs common frontend technologies such as jQuery and Bootstrap 5, providing a responsive and user-friendly interface. However, the site lacks a valid SSL certificate and proper HTTPS configuration, which is a significant security concern. Performance is moderate with a page load time of approximately 4.5 seconds and a moderate number of resources. Accessibility and SEO optimizations are basic, with room for improvement. From a security perspective, the absence of HTTPS and security headers, lack of HSTS, and no evidence of incident response or security policies indicate a low security posture. No privacy or cookie policies are present, and no contact information or certifications are displayed, which impacts trust and compliance. The WHOIS data shows a consistent and mature domain registration, supporting legitimacy but does not compensate for the technical security gaps. Overall, the website demonstrates a functional business offering but requires urgent improvements in security, privacy compliance, and transparency to enhance trustworthiness and protect users. Strategic recommendations include obtaining a valid SSL certificate, implementing security headers, publishing privacy and cookie policies, and providing clear contact information.

Scanned

This is an earlier scan of paymer.com. View the latest report

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

5 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 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 paymer.com

This scan found 19 issues across 5 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
100
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
40
Average
70

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

Total records
1,278
Employees
0
Customers
1,278
Third parties
0
Weak passwords
12%

4 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 paymer.com.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Paymer.com occupies a niche in the digital payments sector, leveraging WebMoney and cryptocurrencies to offer digital checks as a payment instrument. Its competitive advantage lies in the simplicity and security of digital checks that can be transferred multiple times without losing value. The business model is transaction-based, likely generating revenue from commissions on check transfers and payouts. The target market includes both individual users and merchants globally, with no geographic restrictions mentioned. The platform supports merchant integration via payment links and APIs, indicating a focus on e-commerce and online services. The company appears small but established, with a domain age of 24 years. The lack of visible partnerships or subsidiaries suggests a focused operation. Growth potential exists if security and compliance are enhanced to build broader trust.

Security posture

The current security posture of paymer.com is weak due to the lack of HTTPS and valid SSL certificates, absence of security headers, and no HSTS policy. These deficiencies expose users to risks such as data interception and man-in-the-middle attacks. The site does not demonstrate adherence to common security frameworks or incident response readiness, with no contact channels for security issues. No vulnerability disclosure or security.txt files are present. Forms collect sensitive data (check number and code) but without visible security assurances. The absence of privacy and cookie policies further indicates compliance gaps, particularly with GDPR. Immediate remediation is necessary to protect user data and enhance trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Provide clear contact information including support and security incident response channels.
  5. Establish a vulnerability disclosure policy and consider adding a security.txt file to facilitate responsible reporting.
Technical notes

Notes

The website uses a standard frontend stack with jQuery and Bootstrap 5, ensuring responsive design and basic interactivity. The page load time is moderate at 4.5 seconds with 38 resources and a page size of approximately 67 KB, which is acceptable but could be optimized. No modern frameworks or CMS platforms are detected, suggesting a custom or lightweight implementation. The absence of SSL/TLS and security headers is a critical technical debt. No analytics or tracking scripts are present, indicating minimal data collection. The site supports multiple languages (Russian and English) with a language selector implemented via JavaScript. Overall, the technical infrastructure is functional but requires 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

Earlier scans of this domain

  1. 66/100Medium32 findingsView report
Reviews of this site

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