lex.community

We performed a comprehensive analysis of lex.community on 2026-07-06. The website returned an HTTP 200 status code with a server response time of 17540ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 246 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-08-04, which is 29 days from now. The security headers analysis reveals a score of 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing X-Frame-Options and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 6 technologies across 6 categories powering lex.community. The detected stack includes React, Vite, Google Tag Manager, HubSpot, reCAPTCHA v3, and Font Awesome. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, lex.community receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, lex.community receives a trust score of 80/100, which places it in the "Very Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 29 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking) and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked lex.community against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned lex.community and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for lex.community. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for lex.community. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for lex.community. Marketing: HubSpot — provides marketing automation capabilities for lex.community. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for lex.community. Icon Set: Font Awesome — provides additional functionality for lex.community. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KCQN62QS. These IDs can be used to identify other websites operated by the same organization.

lex.community delivers its homepage in 17540ms (server response time), which is considered slow by industry standards. The total page weight is 246 KB, and we detected 152 resource requests loading assets from 9 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 0 out of 44 CSS files and 0 out of 5 JavaScript files are minified. Minifying the remaining 49 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of lex.community produces approximately 0.12g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 246 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for lex.community. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

lex.community resolves to the IPv4 address 188.94.204.84, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 3 name servers: nsa.bookmyname.com, nsb.bookmyname.com, and nsc.bookmyname.com. Having 3 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for lex.community is handled by bookmyname.com with 2 MX records configured: redirmail1.reg.bookmyname.com and redirmail2.reg.bookmyname.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for lex.community, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of lex.community contains 958 words of visible text content. This is a moderate amount of content. The page is structured with 5 H2 headings, 7 H3 headings, 2 H4 headings. The page includes 14 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 20 internal links pointing to other pages on the same domain and 20 external links pointing to third-party websites. There are 5 external JavaScript files, 44 CSS stylesheets, and 1 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on lex.community: Visa. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 3 platforms: Linkedin (@goodflag), Youtube (@UCHufAAAM2k-5QmIq51Bw2gw), and Github (@necolas). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for lex.community is good at 18 characters: "Goodflag Community". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 177 characters (slightly long): "Goodflag Community : conçue pour les particuliers, c'est la plateforme de signature électronique simple, gratuite et séc...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://goodflag.community, preventing duplicate content issues, the page language is declared as fr, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Goodflag Community..."), OG description, These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.