afnor.org

We performed a comprehensive analysis of afnor.org on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 6255ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 350 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by DigiCert Inc (OV 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 2027-03-16, which is 260 days from now. The security headers analysis reveals a score of 100/100 (excellent). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. All recommended security headers are in place, providing comprehensive protection against common web attacks. Our technology detection scan identified 4 technologies across 4 categories powering afnor.org. The detected stack includes Next.js media, React, Vite, and Google Tag Manager. The site uses Next.js as its primary framework (version media). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, afnor.org receives an overall trust score of 82/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, afnor.org receives a trust score of 82/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 DigiCert Inc with 260 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 21.5 years, indicating long-term commitment and legitimacy. Areas of concern include: 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 afnor.org 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. The domain is registered through Gandi SAS based in FR, with a registration date of 2004-12-24 and expiration date of 2026-12-24.

Our technology detection engine scanned afnor.org and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version media) — provides the application framework and routing for afnor.org. UI Library: React — handles the user interface rendering and component management for afnor.org. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for afnor.org. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for afnor.org. We also extracted the following tracking identifiers: Google Tag Manager container GTM-NS28QF6. These IDs can be used to identify other websites operated by the same organization.

afnor.org delivers its homepage in 6255ms (server response time), which is considered slow by industry standards. The total page weight is 350 KB, and we detected 182 resource requests loading assets from 6 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 2 CSS files and 0 out of 33 JavaScript files are minified. Minifying the remaining 35 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. From an environmental perspective, each page view of afnor.org produces approximately 0.17g of CO₂, earning a carbon rating of B. 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 350 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for afnor.org. 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.

afnor.org resolves to the IPv4 address 92.174.137.199, 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: ns-141-c.gandi.net, ns-18-b.gandi.net, and ns-73-a.gandi.net. 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 afnor.org is handled by iphmx.com with 4 MX records configured: mx1.hc1830-88.eu.iphmx.com, mx2.hc1830-88.eu.iphmx.com, and mail.afnor.org and 1 more. 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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for afnor.org, 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 domain is registered through Gandi SAS (FR). It was first registered on 2004-12-24 and is set to expire on 2026-12-24, making it 21.5 years old. Our subdomain enumeration scan discovered 4 active subdomains for afnor.org: api.afnor.org, cdn.afnor.org, mail.afnor.org, and www.afnor.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of afnor.org contains 966 words of visible text content. This is a moderate amount of content. The page is structured with 2 H2 headings, 4 H3 headings, 24 H4 headings, 8 H5, and 0 H6 headings. The page includes 24 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 97 internal links pointing to other pages on the same domain and 12 external links pointing to third-party websites. There are 33 external JavaScript files, 2 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), and Schema.org structured data (WebPage). We detected the following payment methods accepted on afnor.org: JCB. 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 4 platforms: Facebook (@AFNORGroup), Twitter (@AFNOR), Instagram (@groupe_afnor), and Linkedin (@afnor). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for afnor.org is too long at 78 characters: "Groupe AFNOR : normalisation, édition, formation, certification | Groupe AFNOR". At 78 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 144 characters (well-optimized): "Normes volontaires, formation, veille, information professionnelle et technique, évaluation et certification, EFQM, audi...". 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://www.afnor.org/, preventing duplicate content issues, the page language is declared as fr, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Groupe AFNOR..."), OG description, OG image (social sharing thumbnail), OG type (website). 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_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: WebPage. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates. The meta keywords tag contains 5 terms including normalisation, certification, formation, qualité, and RSE. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.