Skip to main content

Security report for paynearme-sandbox.com

PayNearMe, Inc. · Finance · United States

Medium risk. 5 critical or high findings in Email security, GDPR outside view and 1 other check.

Security score

69/100

Risk levelMedium

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

PayNearMe, Inc. operates a payment processing platform that facilitates convenient payment options including cash payments at physical locations. The sandbox environment analyzed is designed for testing and development purposes, reflecting a mature business with a domain established in 2015. The website employs modern web technologies such as jQuery, Google reCAPTCHA v3, and AWS DNS hosting, indicating a solid technical foundation. Security measures include HTTPS enforcement and CSRF tokens on forms, though DNSSEC is not enabled and explicit security headers are absent, suggesting room for improvement in security hardening. Privacy compliance is partially addressed with accessible privacy and terms of service documents on the main domain, but lacks cookie consent mechanisms on the sandbox site. Overall, the website is professional, trustworthy, and safe for general audiences, with moderate tracking via Google Analytics. Strategic recommendations include enhancing DNS security, implementing security headers, and adding cookie consent to improve compliance and security posture.

Scanned

NIS2 and GDPR posture

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

5 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

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

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

Keep watching paynearme-sandbox.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
67
Security headers
80
Email security
40
DNS health
75
Network security
100
GDPR outside view
53
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

Technical appendix

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

Business context

Business profile

PayNearMe positions itself as an important player in the finance and technology sectors, providing payment processing services that cater to both consumers and businesses. Its business model revolves around enabling payments through digital and physical channels, supported by a medium-sized company infrastructure. The sandbox environment supports developer and partner testing, indicating a mature ecosystem. The company benefits from consistent branding, a reputable registrar, and a stable domain age aligned with its founding year. While direct contact information is not present on the sandbox site, the presence of privacy and terms policies on the main domain supports business credibility. The lack of explicit certifications or security policies publicly available suggests potential areas for growth in trust and compliance visibility.

Security posture

The security posture of the website is moderate. HTTPS is properly implemented, and Google reCAPTCHA v3 is used to mitigate automated abuse on login forms. CSRF tokens are present, indicating secure form handling. However, the absence of DNSSEC and missing HTTP security headers such as Content-Security-Policy and Strict-Transport-Security reduce the overall security robustness. No vulnerability disclosure or incident response policies are publicly available, which could impact incident handling readiness. The site does not expose sensitive data in the HTML content, and no vulnerable libraries were detected. Enhancing DNS security and publishing security policies would strengthen the security maturity and compliance posture.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve DNS security.
  2. Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a cookie consent mechanism to comply with GDPR and other privacy regulations.
  4. Publish a public security policy and incident response contact information to improve transparency and trust.
  5. Regularly audit third-party libraries and dependencies to ensure no vulnerabilities are introduced.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PayNearMe, Inc.
Description
PayNearMe provides payment processing services enabling customers to make payments conveniently, including cash payments at physical locations.
Key services
Payment processing, Cash payment locations, Online account management
Content quality
good
Branding
consistent

Technology

Stack
jQuery, jQuery UI, Google reCAPTCHA, Typekit Fonts, AWS DNS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA v3 for login form
  • Form CSRF tokens implemented

Analytics and tracking

Services
Google Analytics 4 (gtag.js)
Tracking level
moderate
Privacy practices
basic

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 sandbox/testing environment for PayNearMe payment services.
  2. No direct contact emails or phone numbers found on the page.
  3. Use of Google reCAPTCHA v3 indicates attention to bot mitigation.
  4. No cookie consent banner or explicit cookie policy found.
  5. Privacy policy and terms of service are hosted on the main paynearme.com domain, not on sandbox subdomain.
  6. No social media links or phone numbers explicitly provided.
  7. No security.txt or vulnerability disclosure policy found.
  8. No explicit security headers detected in HTML content.
  9. DNSSEC not enabled for domain.
Technical notes

Notes

The website uses a modern technology stack including jQuery, jQuery UI, Google reCAPTCHA v3, and Typekit fonts, hosted on AWS infrastructure as indicated by DNS servers. The form structure and CSRF tokens suggest a Ruby on Rails backend. Performance is moderate with asynchronous script loading and CDN usage for common libraries. Mobile optimization and accessibility are basic but functional. SEO optimization is basic with standard meta tags but no Open Graph or JSON-LD structured data detected. The sandbox environment is functional and secure for testing but could benefit from enhanced security headers and privacy features.
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 paynearme-sandbox.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 paynearme-sandbox.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.