unesco.org

We performed a comprehensive analysis of unesco.org on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 20896ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 105 KB. 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.2 with the ECDHE-ECDSA-AES128-GCM-SHA256 cipher suite and ECDSA-SHA384 signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-03, which is 66 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), Referrer-Policy, 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 4 technologies across 4 categories powering unesco.org. The detected stack includes Drupal, Google Tag Manager, Mailchimp, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, unesco.org receives an overall trust score of 75/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, unesco.org receives a trust score of 75/100, which places it in the "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, a valid SSL certificate issued by Let's Encrypt with 66 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked unesco.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.

Our technology detection engine scanned unesco.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. CMS: Drupal — manages the content and page structure for unesco.org. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for unesco.org. Email Marketing: Mailchimp — manages email campaigns and subscriber lists for unesco.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for unesco.org. We also extracted the following tracking identifiers: Google Tag Manager container GTM-T9NW. These IDs can be used to identify other websites operated by the same organization.

unesco.org delivers its homepage in 20896ms (server response time), which is considered slow by industry standards. The total page weight is 105 KB, and we detected 187 resource requests loading assets from 13 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. No compression is currently enabled on unesco.org. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 4 CSS files and 1 out of 3 JavaScript files are minified. Minifying the remaining 6 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 unesco.org produces approximately 0.05g 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 105 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for unesco.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.

unesco.org resolves to the IPv4 address 193.242.192.41, 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 4 name servers: ns-nadc.unicc.org, ns.unicc.org, ns0.unesco.org, and ns1.unesco.org. Having 4 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 unesco.org is handled by Microsoft 365 with 1 MX records configured: unesco-org.mail.protection.outlook.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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for unesco.org. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions. Our subdomain enumeration scan discovered 6 active subdomains for unesco.org: community.unesco.org, ftp.unesco.org, portal.unesco.org, shop.unesco.org, support.unesco.org, and www.unesco.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of unesco.org contains 1,062 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 8 H2 headings, 0 H3 headings, 0 H4 headings, 1 H5, and 0 H6 headings. The page includes 36 images. 28 images (78%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 22% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 104 internal links pointing to other pages on the same domain and 26 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 3 external JavaScript files, 4 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Schema.org structured data (VideoObject), and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on unesco.org: Discover. 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 5 platforms: Facebook (@unesco), Twitter (@UNESCO), Instagram (@unesco), Linkedin (@unesco), and Tiktok (@unesco). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for unesco.org is too long at 93 characters: "UNESCO : Building Peace through Education, Science and Culture, communication an...". At 93 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 206 characters (slightly long): "Learn more about UNESCO's role, vision and results. UNESCO is the United Nations Educational, Scientific and Cultural Or...". 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.unesco.org/en, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: 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: VideoObject. 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.