Skip to main content

Security report for paypalobjects.com

Other · N/a

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

Security score

72/100

Risk levelMedium

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

The analyzed domain www.paypalobjects.com currently returns a 403 Forbidden error page with minimal HTML content, indicating that access to the site is blocked or restricted. The page contains no metadata, structured data, forms, or contact information, and only includes a single external link to the main PayPal website. The WHOIS query for this domain returned no match, suggesting the domain may be unregistered, protected, or otherwise inaccessible publicly. This lack of WHOIS data and website content severely limits the ability to assess the domain's legitimacy or business operations. From a technical perspective, the site does not expose any detectable technologies, scripts, or security headers, and no SSL or hosting information is available. The absence of privacy, cookie, or terms of service policies further indicates that this subdomain is not intended for public interaction or business use. The content safety rating is safe due to the lack of any content, including adult or explicit material. Security posture is poor due to the lack of accessible content and absence of security best practices. The domain's WHOIS data absence and the 403 error page reduce trust and legitimacy scores significantly. Overall, this domain appears to be a restricted or internal resource rather than a public-facing website, limiting the scope of analysis and raising concerns about transparency and accessibility. Strategic recommendations include ensuring proper domain registration and WHOIS data availability, providing accessible content for analysis, implementing security headers and compliance policies, and publishing contact and incident response information to improve trust and security posture.

Scanned

NIS2 and GDPR posture

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

6 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 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';…
  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 paypalobjects.com

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. 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
82
Security headers
45
Email security
70
DNS health
85
Network security
100
GDPR outside view
50
Average
72

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

Due to the lack of accessible content and WHOIS data, no meaningful business intelligence can be derived from this domain. The domain name suggests affiliation with PayPal, a major financial technology company specializing in online payments and financial services. However, without accessible content or registration data, it is impossible to confirm the domain's role, market positioning, or business model. No information on partnerships, subsidiaries, or growth indicators is available.

Security posture

The security posture of the domain is currently poor due to the absence of accessible content and security headers. The 403 Forbidden error page indicates restricted access, which may be intentional for security reasons. However, no security policies, incident response contacts, or vulnerability disclosures are present. The lack of WHOIS data further complicates trust assessment. No SSL or HTTPS information is available from the provided data. Overall, the domain does not demonstrate publicly visible security best practices or compliance measures.

Recommendations

  1. Ensure the domain is properly registered and WHOIS data is publicly available to improve transparency.
  2. Make website content accessible or provide a landing page with relevant business and compliance information.
  3. Implement and expose standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish privacy, cookie, and terms of service policies to enhance compliance and user trust.
  5. Provide clear contact information and incident response channels to improve security posture and user confidence.
Site observations

Automated reading of the public site. Ratings are indicative.

None detected. Website returns a 403 Forbidden error page with minimal content, indicating access is blocked or restricted. No explicit WAF vendor detected. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, structured data, or forms present.
  3. No contact information or policies found on the page.
  4. No scripts or external libraries detected in the HTML.
  5. Only one external link to www.paypal.com detected.
  6. No security headers or SSL configuration details available.
  7. WHOIS data unavailable, indicating domain may be unregistered or protected.
  8. Content safety is rated safe due to lack of content.
  9. WAF or security blocking likely but no vendor identified.
Technical notes

Notes

The website currently serves a minimal HTML 403 error page with no metadata, scripts, or structured data. No CMS, frameworks, or hosting provider information is detectable. The lack of external scripts or analytics tools suggests minimal technical infrastructure on this subdomain. The site is not optimized for mobile or SEO due to the absence of content. Performance and accessibility cannot be assessed due to the blocked content. The domain appears to be either restricted or not intended for public use.
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. 72/100 +1Medium27 findingsView report
  2. 71/100 −4Medium28 findingsView report
  3. 75/100Medium21 findingsView report
Reviews of this site

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