screamer.wiki

We performed a comprehensive analysis of screamer.wiki on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 11576ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 33 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-09-15, which is 70 days from now. The security headers analysis reveals a score of 35/100 (below average). The following security headers are properly configured: Strict-Transport-Security (HSTS) and X-Content-Type-Options. However, the site is missing Content-Security-Policy, X-Frame-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 1 technologies across 1 categories powering screamer.wiki. The detected stack includes jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, screamer.wiki receives an overall trust score of 72/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, screamer.wiki receives a trust score of 72/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 70 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. 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, 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 screamer.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 screamer.wiki and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. JavaScript Library: jQuery — provides utility functions and DOM manipulation for screamer.wiki.

screamer.wiki delivers its homepage in 11576ms (server response time), which is considered slow by industry standards. The total page weight is 33 KB, and we detected 107 resource requests loading assets from 11 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 2 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 3 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 screamer.wiki produces approximately 0.02g 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 33 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for screamer.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.

screamer.wiki resolves to the IPv4 address 95.216.36.61 and also supports IPv6 (2a01:4f9:2a:2470::2), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 4 name servers: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, and salvador.ns.porkbun.com. 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. 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 is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 screamer.wiki. 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 screamer.wiki contains 922 words of visible text content. This is a moderate amount of content. The page is structured with 6 H2 headings, 0 H3 headings, 1 H4 headings. The page includes 10 images. 2 images (20%) 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 80% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 71 internal links pointing to other pages on the same domain and 18 external links pointing to third-party websites. There are 1 external JavaScript files, 2 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 (Article, ImageObject, Organization, and SearchAction), 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. The website has social media presence across 1 platforms: Youtube (@ScreamerWiki). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for screamer.wiki is good at 13 characters: "Screamer Wiki". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for screamer.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 page language is declared as en and the meta robots directive is set to max-image-preview:standard. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Screamer Wiki..."), 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 site implements Schema.org structured data with the following types: Article, ImageObject, Organization, and SearchAction. 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 13 terms including "Screamer wiki, Screamer, Internet screamer, Internet screamers, and Screamer fandom. 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.