yeswiki.net

We performed a comprehensive analysis of yeswiki.net on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 10212ms. The page is served over HTTP/2 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 64 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.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-07-19, which is 19 days from now. The security headers analysis reveals a score of 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Permissions-Policy. However, the site is missing Referrer-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 5 categories powering yeswiki.net. The detected stack includes React, Vue.js, Bootstrap, Matomo, jQuery, 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, yeswiki.net receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, yeswiki.net 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 19 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: 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 yeswiki.net 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 yeswiki.net and identified 6 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. UI Library: React and Vue.js — handles the user interface rendering and component management for yeswiki.net. CSS Framework: Bootstrap — provides the styling and responsive layout system for yeswiki.net. Analytics: Matomo — tracks visitor behavior and provides traffic insights for yeswiki.net. JavaScript Library: jQuery — provides utility functions and DOM manipulation for yeswiki.net. Icon Set: Font Awesome — provides additional functionality for yeswiki.net.

yeswiki.net delivers its homepage in 10212ms (server response time), which is considered slow by industry standards. The total page weight is 64 KB, and we detected 108 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. No compression is currently enabled on yeswiki.net. 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: 3 out of 13 CSS files and 6 out of 14 JavaScript files are minified. Minifying the remaining 18 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 yeswiki.net 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 64 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for yeswiki.net. 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.

yeswiki.net resolves to the IPv4 address 195.201.63.240 and also supports IPv6 (2a01:4f8:13b:24e::2), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 3 name servers: ns-134-b.gandi.net, ns-157-a.gandi.net, and ns-176-c.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 yeswiki.net is handled by infomaniak.ch with 1 MX records configured: mta-gw.infomaniak.ch. 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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for yeswiki.net. 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.

The homepage of yeswiki.net contains 485 words of visible text content. This is a moderate amount of content. The page is structured with 5 H2 headings, 2 H3 headings, 5 H4 headings. The page includes 4 images. 1 images (25%) 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 75% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 40 internal links pointing to other pages on the same domain and 9 external links pointing to third-party websites. There are 14 external JavaScript files, 13 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: RSS feed for content syndication. Notable missing features: XML Sitemap, 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 1 platforms: Github (@YesWiki). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for yeswiki.net is good at 28 characters: "YesWiki.net : PagePrincipale". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 154 characters (well-optimized): "Publiez, éditez et partagez vos contenus. YesWiki est un outil libre et convivial pour construire des plateformes de par...". 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://yeswiki.net/?pageprincipale, 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 ("YesWiki.net..."), OG type (article). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. The meta keywords tag contains 6 terms including ferme, YesWiki, libre, php, and no-code. 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.