Skip to main content

Security report for colliers.com

Just a moment... · Real Estate · N/a

Medium risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

51/100

Risk levelMedium

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

The website colliers.com is currently inaccessible due to a Cloudflare Web Application Firewall (WAF) security challenge page that requires JavaScript and cookies to be enabled. This prevents access to any substantive content, metadata, or business information on the site. The domain is registered and uses Cloudflare as a hosting and security provider, but the SSL/TLS certificate is invalid or missing, which is a critical security issue. No privacy, cookie, or terms of service policies are detectable in the accessible content. The DNS records indicate legitimate domain usage with multiple marketing and verification TXT records, suggesting active business operations. However, the lack of accessible content and invalid SSL significantly limit the ability to assess the company's digital maturity, security posture, and compliance status. Overall, the site’s security posture is basic due to security headers but critically undermined by SSL issues and content blocking.

Scanned

This is an earlier scan of colliers.com. View the latest report

NIS2 and GDPR posture

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

    • 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

  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 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 colliers.com

This scan found 14 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
0
Security headers
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
15
Average
51

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.

Brand lookalikes

Add-on

Domains that imitate colliers.com and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
34
Registered
34
Resolving
34
High or critical
0

Last checked 2026-06-26

Masked preview

  • cc•••••••.comMediumrepetition
  • co••••••.comMediumbitsquatting
  • co••••••.comMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of colliers.com with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

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

Due to the Cloudflare challenge blocking access, detailed business intelligence is unavailable. The domain is associated with the real estate sector, likely representing a large enterprise given the domain and DNS complexity. The presence of multiple marketing verification records suggests a mature marketing and partnership ecosystem. However, no direct business model, revenue streams, or customer segmentation data can be extracted from the blocked content. The domain registration data is consistent with a legitimate business entity, with no privacy protection or suspicious patterns detected.

Security posture

The security posture shows some positive indicators such as multiple security headers (X-Frame-Options, Content-Type-Options, Permissions-Policy) and use of Cloudflare’s security services. However, the absence of a valid SSL certificate and lack of modern TLS protocols severely degrade security. No HSTS is enabled, and session resumption and OCSP stapling are missing. The site lacks publicly accessible security policies or incident response contacts. The Cloudflare WAF challenge indicates active protection against automated threats but also blocks content access, limiting transparency. Overall, the security maturity is low with critical gaps in encryption and policy disclosure.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate supporting TLS 1.2 or TLS 1.3 to secure communications.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  3. Publish accessible privacy, cookie, terms of service, and security policies to improve compliance and trust.
  4. Implement a security.txt file and vulnerability disclosure policy to facilitate responsible reporting.
  5. Review Cloudflare WAF settings to balance security with user accessibility and SEO considerations.
Technical notes

Notes

The website is hosted behind Cloudflare, which provides DNS, CDN, and security services. The SSL configuration is invalid, and no modern TLS protocols are supported. The HTTP headers show a strong permissions policy restricting many browser features, and security headers are present. However, the site content is blocked by a Cloudflare JavaScript challenge, preventing analysis of HTML structure, forms, metadata, or scripts. No CMS or frameworks are detectable from the limited accessible content. Performance metrics are unavailable due to content blocking. The site lacks SEO metadata and structured data, indicating either a temporary block or misconfiguration. Overall, the technical infrastructure relies heavily on Cloudflare but requires improvements in SSL and content accessibility.
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. 83/100Low23 findingsView report
Reviews of this site

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