runescape.wiki

We performed a comprehensive analysis of runescape.wiki on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 8127ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 55 KB, and the site is served behind a CDN (Content Delivery Network). 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-06, which is 38 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 Referrer-Policy. However, the site is missing 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 runescape.wiki. The detected stack includes jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, runescape.wiki receives an overall trust score of 76/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, runescape.wiki receives a trust score of 76/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 38 days until expiration, and DNSSEC providing authenticated DNS responses. Areas of concern include: 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 runescape.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 runescape.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 runescape.wiki.

runescape.wiki delivers its homepage in 8127ms (server response time), which is considered slow by industry standards. The total page weight is 55 KB, and we detected 214 resource requests loading assets from 7 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 3 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 4 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of runescape.wiki 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 55 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for runescape.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.

runescape.wiki resolves to the IPv4 address 104.20.39.105 and also supports IPv6 (2606:4700:10::6814:2769), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: naomi.ns.cloudflare.com and tom.ns.cloudflare.com. 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. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. 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 enabled for runescape.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. Our subdomain enumeration scan discovered 1 active subdomains for runescape.wiki: www.runescape.wiki. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of runescape.wiki contains 812 words of visible text content. This is a moderate amount of content. The page is structured with 16 H2 headings, 13 H3 headings, 0 H4 headings. The page includes 28 images. 26 images (93%) 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 7% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 154 internal links pointing to other pages on the same domain and 18 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 1 external JavaScript files, 3 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (WebSite). 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: Twitter (@RSWiki). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for runescape.wiki is good at 18 characters: "The RuneScape Wiki". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 215 characters (slightly long): "We are the official RuneScape encyclopaedia, written and maintained by the players. Since our start in 2005, we've becom...". 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://runescape.wiki/, preventing duplicate content issues, the page language is declared as en-gb, the meta robots directive is set to max-image-preview:standard, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("RuneScape Wiki..."), OG description, OG image (social sharing thumbnail), 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. The site implements Schema.org structured data with the following types: 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.