sipri.org

We performed a comprehensive analysis of sipri.org on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 9757ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 71 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Sectigo Limited (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 2 domain(s) (Subject Alternative Names) and expires on 2027-02-04, which is 220 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 sipri.org. The detected stack includes Drupal, Matomo, jQuery, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, sipri.org receives an overall trust score of 73/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, sipri.org receives a trust score of 73/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 Sectigo Limited with 220 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, 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 sipri.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 sipri.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 sipri.org. Analytics: Matomo — tracks visitor behavior and provides traffic insights for sipri.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for sipri.org. Icon Set: Font Awesome — provides additional functionality for sipri.org.

sipri.org delivers its homepage in 9757ms (server response time), which is considered slow by industry standards. The total page weight is 71 KB, and we detected 188 resource requests loading assets from 8 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 8 CSS files and 5 out of 37 JavaScript files are minified. Minifying the remaining 40 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 sipri.org produces approximately 0.03g 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 71 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for sipri.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.

sipri.org resolves to the IPv4 address 193.10.14.94, 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: ns1.sipri.org, ns2.sipri.org, and sunic.sunet.se. 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 sipri.org is handled by Microsoft 365 with 1 MX records configured: sipri-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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 sipri.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 sipri.org: admin.sipri.org, apps.sipri.org, dev.sipri.org, mail.sipri.org, support.sipri.org, and www.sipri.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of sipri.org contains 447 words of visible text content. This is a moderate amount of content. The page is structured with 5 H2 headings, 8 H3 headings, 0 H4 headings. The page includes 17 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 111 internal links pointing to other pages on the same domain and 10 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 37 external JavaScript files, 8 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). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 4 platforms: Facebook (@sipri.org), Twitter (@SIPRIorg), Instagram (@sipriorg), and Linkedin (@sipri). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for sipri.org is good at 12 characters: "Home | SIPRI". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 101 characters (well-optimized): "Stockholm International Peace Research Institute (SIPRI): the independent resource on global security". 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.sipri.org/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Home..."), OG description, OG image (social sharing thumbnail), 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 meta keywords tag contains 10 terms including arms, weapons, disarmament, global, and security. 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.