Skip to main content

Security report for hairandmakeup.com.au

Hair & Makeup by Lois Poulsen · Hospitality · Australia

High risk. 10 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

31/100

Risk levelHigh

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

Hair & Makeup by Lois Poulsen is a small Australian business specializing in professional hair and makeup services primarily for weddings, formals, special events, and photo shoots in the Brisbane and Gold Coast regions. The website presents a clear business focus with detailed service descriptions and customer testimonials, targeting individuals seeking mobile and venue-based beauty services. The technical infrastructure is based on Joomla CMS with modern frontend libraries such as Bootstrap and jQuery, hosted on a LiteSpeed server. However, the website lacks a valid SSL certificate, serving content over HTTP only, which significantly impacts security and trustworthiness. Security headers are minimal, and no advanced security or privacy policies are present. The absence of privacy and cookie policies indicates non-compliance with GDPR and related regulations. Overall, the site is functional and professionally presented but requires urgent security and compliance improvements.

Scanned

NIS2 and GDPR posture

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

10 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching hairandmakeup.com.au

This scan found 17 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
0
Security headers
30
Email security
50
DNS health
85
Network security
20
GDPR outside view
0
Average
31

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 hospitality sector, focusing on personal grooming and event services. It leverages a mobile service model to reach clients at their venues, enhancing convenience and market reach. The website content and testimonials suggest a strong local reputation and expertise, particularly with over 20 years of professional experience. The business maintains social media presence on Facebook and encourages customer reviews via Google. The lack of detailed company registration or VAT information is typical for small service providers. The website is designed to convert visitors through clear calls to action and service descriptions, but lacks advanced marketing or analytics tools.

Security posture

The current security posture is weak due to the absence of HTTPS, lack of HSTS, and missing advanced security headers. While cookies are set with Secure and HttpOnly flags, the lack of TLS support exposes users to potential interception risks. No vulnerability disclosure or incident response policies are published, indicating limited security governance. The server uses PHP 8.1.31, which is a modern version, but no information about patching or firewall protections is available. The site does not implement DNSSEC or CAA records, which could improve DNS security. Overall, the site is vulnerable to man-in-the-middle attacks and lacks compliance with modern security best practices.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement and publish privacy and cookie policies to comply with GDPR and other privacy regulations.
  3. Enable HSTS with includeSubDomains and preload options to enforce HTTPS usage.
  4. Add security headers such as Content-Security-Policy, Referrer-Policy, and X-Frame-Options.
  5. Establish a vulnerability disclosure policy or security.txt file to improve transparency and incident response readiness.
Technical notes

Notes

The website is built on Joomla CMS with PHP 8.1.31 and served by a LiteSpeed web server. Frontend technologies include jQuery and Bootstrap 5.3.2, with custom modules like PageBuilder CK and Maximenu CK for layout and navigation. The site is mobile responsive and uses Google Fonts. Performance metrics are missing, but the lack of caching headers and no CDN usage suggest moderate to slow load times. The DNS setup is standard with no DNSSEC or CAA records. The SSL configuration is absent, which is a critical technical deficiency. The site uses secure and HttpOnly cookies but lacks session resumption and OCSP stapling. Overall, the technical stack is modern but security and performance optimizations are needed.
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 hairandmakeup.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 hairandmakeup.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.