Security report for crexi.com
Crexi · Real Estate · N/a
Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.
Crexi operates as an online commercial real estate exchange platform, providing photos, maps, and property descriptions to facilitate real estate transactions. The website targets commercial real estate professionals and investors, positioning itself as a significant player in the real estate marketplace sector. The business model revolves around listing and exchanging commercial properties, leveraging digital tools to enhance market visibility and transaction efficiency. The platform's market position appears established, though specific company founding details and country of operation are not explicitly stated in the analyzed content. Technically, the website employs modern web technologies including Angular framework, Google Maps API for geospatial data, Stripe for payment processing, and various marketing and analytics tools such as Google Analytics, HubSpot, and Trustpilot widgets. The technical infrastructure supports a moderate performance level with basic mobile optimization and SEO practices. However, the absence of a detected CMS and hosting provider details limits a full assessment of the backend environment. From a security perspective, the site uses HTTPS and integrates reCAPTCHA v3 to mitigate automated abuse. Nonetheless, there is a lack of visible security headers and no published security or incident response policies, which are critical for a platform handling sensitive business data. The WHOIS data is notably absent or inaccessible, raising concerns about domain registration transparency and legitimacy. This gap impacts the overall trustworthiness and may warrant further investigation. Overall, while the platform demonstrates a professional business presence with essential digital tools, it exhibits gaps in privacy compliance, security best practices, and domain registration transparency. Addressing these areas will enhance trust, regulatory compliance, and security posture, thereby supporting sustainable business growth and user confidence.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 50/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
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
- RFC 6797 §6.1.1
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- 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';…
- High
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
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
Third-party services without privacy policy
Detected services: Google Analytics, Twitter, Google APIs, Google Ads
What to do: Document all third-party data sharing in your privacy policy
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching crexi.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. 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
- 75
- Security headers
- 55
- Email security
- 75
- DNS health
- 85
- Network security
- 100
- GDPR outside view
- 50
- Average
- 73
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
Security posture
Recommendations
- Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance web security.
- Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and user consent mechanisms.
- Establish and publicize a vulnerability disclosure program and security.txt file to facilitate responsible reporting and incident management.
- Improve WHOIS domain registration transparency to strengthen legitimacy and trustworthiness.
- Conduct regular security audits of third-party scripts and marketing tools to minimize vulnerabilities and data leakage.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Crexi
- Description
- Photos, maps, description for commercial real estate
- Key services
- Commercial real estate listings, Property photos, Maps and location data, Property descriptions
- Content quality
- basic
- Branding
- consistent
Technology
- Stack
- Google Maps API, Stripe, Google Analytics, Google Tag Manager, Trustpilot widget, Branch.io, Twitter Ads, Bing Ads
- Frameworks
- Angular (implied by ngcontent attributes), Material Icons
- Performance
- moderate
- Mobile
- basic
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 60/100
- Good practices seen
- Use of HTTPS (implied by Google services usage)
- Use of reCAPTCHA v3
Analytics and tracking
- Services
- Google Analytics, HubSpot Analytics
- Tracking level
- extensive
- Privacy practices
- poor
Advertising
- Ad networks
- Google Ads, Bing Ads, Twitter Ads
- Tracking pixels
- Trustpilot
- Marketing tools
- HubSpot forms and analytics, Branch.io
- Transparency
- basic
Site quality
- Design
- basic
- User experience
- basic
- Content relevance
- basic
- Navigation
- basic
- Professionalism
- basic
- Trustworthiness
- moderate
Key observations
- Website content is minimal and primarily a placeholder with title and meta description.
- No privacy, cookie, or terms of service policies found in the provided HTML content.
- No contact emails, phone numbers, or physical addresses explicitly found in the HTML content.
- Multiple third-party marketing and analytics scripts are loaded, indicating extensive user tracking.
- No explicit security headers or advanced security configurations detected in the provided data.
- WHOIS data is missing or inaccessible, raising concerns about domain registration transparency.
- Website uses modern technologies such as Angular framework and Google Maps API.
- No signs of adult or NSFW content; content is safe and business-focused.
- No WAF or blocking mechanisms detected; content is accessible.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 68/100Medium25 findingsView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with crexi.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review crexi.com.