promuze.wiki

We performed a comprehensive analysis of promuze.wiki on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 9196ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 251 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 ECDSA-SHA384 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-21, which is 48 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, 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 8 technologies across 7 categories powering promuze.wiki. The detected stack includes WordPress 7.0, WooCommerce, Webpack, Vite, Google Analytics 4, Google Fonts, jQuery, and Font Awesome. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, promuze.wiki receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, promuze.wiki receives a trust score of 68/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 48 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), missing Referrer-Policy, potentially leaking URL information to third parties, and 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 promuze.wiki 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 promuze.wiki and identified 8 distinct technologies across 7 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 promuze.wiki. Ecommerce: WooCommerce — powers the online store and shopping functionality for promuze.wiki. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for promuze.wiki. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for promuze.wiki. Fonts: Google Fonts — delivers web fonts for typography for promuze.wiki. JavaScript Library: jQuery — provides utility functions and DOM manipulation for promuze.wiki. Icon Set: Font Awesome — provides additional functionality for promuze.wiki.

promuze.wiki delivers its homepage in 9196ms (server response time), which is considered slow by industry standards. The total page weight is 251 KB, and we detected 299 resource requests loading assets from 30 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: 5 out of 19 CSS files and 10 out of 23 JavaScript files are minified. Minifying the remaining 27 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 promuze.wiki produces approximately 0.12g 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 251 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for promuze.wiki. 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.

promuze.wiki resolves to the IPv4 address 217.11.249.137, 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 2 name servers: ns2.blueboard.cz and shinzon.blueboard.cz. Having 2 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 promuze.wiki is handled by blueboard.cz with 1 MX records configured: mx.blueboard.cz. 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 enabled for promuze.wiki, 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 homepage of promuze.wiki contains 822 words of visible text content. This is a moderate amount of content. The page is structured with 6 H2 headings, 32 H3 headings, 0 H4 headings. The page includes 6 images. 1 images (17%) 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 83% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 193 internal links pointing to other pages on the same domain and 33 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 23 external JavaScript files, 19 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), Schema.org structured data (ImageObject, SearchAction, WebSite, and organization), AMP (Accelerated Mobile Pages) version, and RSS feed for content syndication. The website has social media presence across 6 platforms: Facebook (@envato), Twitter (@envato), Instagram (@envato), Linkedin (@envato), Youtube (@envato), and Pinterest (@envato). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for promuze.wiki is good at 8 characters: "pro muže". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for promuze.wiki. 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://promuze.wiki/, preventing duplicate content issues, the page language is declared as cs, the meta robots directive is set to index, follow, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to promuze.wiki on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The site implements Schema.org structured data with the following types: ImageObject, SearchAction, WebSite, and organization. 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 1 terms including wiki. 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.