Skip to main content

Security report for openpay.com.au

Finance · Australia

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

62/100

Risk levelMedium

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

The website openpay.com.au currently presents a minimal and essentially blank page with no visible content, metadata, or user-facing information. This severely limits the ability to assess the business operations or services directly from the site. Based on the domain and WHOIS data, the domain is registered through a reputable Australian registrar and is consistent with a legitimate finance-related business operating in Australia. However, the lack of content and security features indicates the website may be under construction or improperly configured. From a technical perspective, the site lacks any detectable technologies, scripts, or frameworks. There is no evidence of HTTPS or security headers, which are critical for protecting user data and establishing trust. The absence of privacy, cookie, or terms of service policies further reduces compliance with data protection regulations such as GDPR. Security posture is weak due to missing HTTPS and security headers, no visible incident response or vulnerability disclosure information, and no contact details for security or business inquiries. The site does not appear to employ any analytics or advertising technologies, which may be due to its minimal state. Overall, the website poses a low trust and credibility level in its current form. Strategic recommendations include implementing HTTPS, publishing essential policies, adding contact information, and enhancing content quality to improve user trust and compliance. Until these improvements are made, the site should be considered incomplete and not fully operational.

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

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

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

Keep watching openpay.com.au

This scan found 23 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
72
Security headers
15
Email security
65
DNS health
70
Network security
100
GDPR outside view
50
Average
62

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

Total records
508
Employees
0
Customers
479
Third parties
29
Weak passwords
6%

5 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 openpay.com.au.

Select it in the checkout above.

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

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

Openpay.com.au appears to be associated with the finance sector, likely providing payment or financial services in Australia. The domain registration through DROP.com.au and the Australian name servers support this geographic focus. However, the lack of visible business information, descriptions, or service details on the website limits insight into its market positioning or business model. There are no detected partnerships or subsidiaries linked through the website content. The absence of marketing or analytics tools suggests limited digital maturity or an early stage of website deployment.

Security posture

The current security posture of the website is poor. There is no evidence of HTTPS or SSL/TLS encryption, no security headers, and no published security policies or incident response contacts. The absence of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. No vulnerability disclosure or security.txt files are present. These gaps expose the site to potential risks including data interception, lack of user trust, and regulatory penalties. The WHOIS data does not indicate privacy protection, which is appropriate for a finance-related business, but the lack of security controls on the website itself is a critical weakness.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all communications.
  2. Publish comprehensive privacy, cookie, and terms of service policies to ensure regulatory compliance.
  3. Add clear contact information including support and security incident response channels.
  4. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Enhance website content quality and metadata to improve SEO, user trust, and business credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor

Technology

SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is minimal and essentially blank with no metadata or visible content.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms present on the page.
  4. No scripts or external resources detected in the HTML.
  5. No SEO or accessibility features detected.
  6. WHOIS data is structured and indicates a legitimate domain registration.
  7. No security headers or HTTPS information available from provided data.
  8. No advertising or analytics technologies detected.
  9. No social media or external links found in the HTML content.
  10. Website appears to be a placeholder or under construction.
Technical notes

Notes

The website currently lacks any detectable technical infrastructure beyond a basic HTML skeleton. No CMS, frameworks, or third-party scripts are present. The WHOIS data shows the domain is registered with a reputable Australian registrar and uses standard name servers. There is no information on hosting provider or performance metrics. The absence of meta tags, Open Graph, or structured data indicates poor SEO and digital maturity. The site is not optimized for mobile or accessibility based on the minimal content. Technical modernization and infrastructure deployment are necessary to support business operations effectively.
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 openpay.com.au. 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 openpay.com.au.

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.