wassenaar.org

We performed a comprehensive analysis of wassenaar.org on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 23270ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 66 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 2 domain(s) (Subject Alternative Names) and expires on 2026-12-25, which is 179 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 5 technologies across 5 categories powering wassenaar.org. The detected stack includes WordPress 7.0, WooCommerce, Matomo, Google Fonts, and jQuery 3.5.1.. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, wassenaar.org receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, wassenaar.org 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 DigiCert Inc with 179 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none policy. Areas of concern include: 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 wassenaar.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 wassenaar.org and identified 5 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 7.0) — manages the content and page structure for wassenaar.org. Ecommerce: WooCommerce — powers the online store and shopping functionality for wassenaar.org. Analytics: Matomo — tracks visitor behavior and provides traffic insights for wassenaar.org. Fonts: Google Fonts — delivers web fonts for typography for wassenaar.org. JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for wassenaar.org.

wassenaar.org delivers its homepage in 23270ms (server response time), which is considered slow by industry standards. The total page weight is 66 KB, and we detected 148 resource requests loading assets from 3 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: 2 out of 8 CSS files and 6 out of 15 JavaScript files are minified. Minifying the remaining 15 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 wassenaar.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 66 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for wassenaar.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.

wassenaar.org resolves to the IPv4 address 193.70.40.129, 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: dns1.a1.net, dns2.a1.net, and dns3.a1.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 wassenaar.org is handled by wassenaar.org with 2 MX records configured: mail.wassenaar.org and mx3.bon.at. 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 not enabled for wassenaar.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 2 active subdomains for wassenaar.org: mail.wassenaar.org and www.wassenaar.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of wassenaar.org contains 309 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 9 H3 headings, 3 H4 headings. The page includes 27 images. 12 images (44%) 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 56% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 82 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 15 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (BreadcrumbList, EntryPoint, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite) and RSS feed for content syndication. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: Linkedin (@wassenaar-arrangement). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for wassenaar.org is well-optimized at 32 characters: "Home - The Wassenaar Arrangement". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for wassenaar.org. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The canonical url is correctly set to https://www.wassenaar.org/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Home - The Wassenaar Arrangement..."), OG description, 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: BreadcrumbList, EntryPoint, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite. 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.