Skip to main content

Security report for searchengine.com.au

Search engine optimisation natural organic search specialists Google Bing Yahoo · Other · Australia

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

Security score

62/100

Risk levelMedium

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

The website searchengine.com.au operates as a small-scale SEO service provider specializing in natural organic search optimization for major search engines such as Google, Bing, and Yahoo. The business targets companies seeking to improve their online visibility through SEO consulting and marketing services. The site content and structure indicate a niche market position with basic service offerings and moderate branding consistency. Technically, the website uses legacy technologies such as jQuery and jHtmlArea, hosted on an nginx server with a valid SSL certificate but lacking modern TLS protocol support. Performance is fast, but mobile optimization and accessibility are basic. Security headers include HSTS, but DNSSEC and CAA records are not implemented, and no advanced security policies or privacy compliance mechanisms are present. The site uses Google Analytics for tracking without visible privacy or cookie consent mechanisms, indicating potential compliance gaps. Overall, the security posture is basic with room for significant improvements in encryption protocols, policy disclosures, and data protection practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

7 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 searchengine.com.au

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
77
Security headers
30
Email security
70
DNS health
85
Network security
85
GDPR outside view
25
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

Technical appendix

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

Business context

Business profile

The business operates in the SEO and online marketing sector within Australia, focusing on organic search optimization. Its competitive advantage lies in specialized SEO knowledge, targeting small to medium businesses aiming to improve search rankings. Revenue streams likely derive from consulting and marketing services. The partnership ecosystem includes domain registration and DNS service providers, enhancing credibility. However, the lack of visible contact information and policy disclosures may limit customer trust and growth potential. The business model is service-oriented with a focus on organic search marketing, but the dated website and limited digital maturity suggest opportunities for modernization and expansion.

Security posture

The current security maturity level is basic, with a valid SSL certificate and HSTS enabled but lacking support for modern TLS versions and advanced security headers such as CSP. DNSSEC and CAA are not enabled, reducing DNS security. No privacy, cookie, or terms of service policies are present, indicating compliance gaps with GDPR and other data protection regulations. Incident response and vulnerability disclosure mechanisms are absent. The use of Google Analytics without consent mechanisms further exposes privacy risks. Overall, the security culture appears minimal, with significant improvements needed to meet modern standards and regulatory requirements.

Recommendations

  1. Enable TLS 1.2 or TLS 1.3 protocols to improve encryption security.
  2. Implement DNSSEC and CAA records to enhance DNS and certificate security.
  3. Publish comprehensive privacy, cookie, and terms of service policies with GDPR compliance.
  4. Add Content Security Policy (CSP) and other security headers to mitigate web vulnerabilities.
  5. Establish incident response and vulnerability disclosure processes to improve security readiness.
Technical notes

Notes

The website infrastructure is based on nginx hosting with legacy JavaScript libraries such as jQuery and jHtmlArea. The SSL certificate is valid but uses an unknown algorithm and lacks support for modern TLS protocols, which is a technical debt and security risk. Performance metrics indicate fast load times, but no mobile optimization or accessibility enhancements are evident. The absence of CMS or modern frameworks suggests a static or custom-built site with limited scalability. The use of Google Analytics indicates basic analytics integration but lacks privacy compliance features. Overall, the technical stack is outdated and would benefit from modernization to improve security, performance, and user experience.
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 searchengine.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 searchengine.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.