itemdb.biz

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, itemdb.biz receives a trust score of 79/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, 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 itemdb.biz 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.

🤖 AI Summary

Our automated technology detection scan was unable to identify specific technologies on itemdb.biz. This could indicate that the site uses server-side rendering without client-side technology fingerprints, employs aggressive code obfuscation, or uses custom-built solutions that don't match known technology signatures.

🤖 AI Summary

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

🤖 AI Summary

itemdb.biz resolves to the IPv4 address 172.67.190.180 and also supports IPv6 (2606:4700:3036::ac43:beb4), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: phil.ns.cloudflare.com and vida.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 (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 (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is enabled for itemdb.biz, 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 25 active subdomains for itemdb.biz: admin.itemdb.biz, api.itemdb.biz, app.itemdb.biz, apps.itemdb.biz, blog.itemdb.biz, cdn.itemdb.biz, community.itemdb.biz, and dev.itemdb.biz. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of itemdb.biz contains 90 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 3 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 1 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Progressive Web App (PWA) manifest (enabling app-like installation). 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: Twitter (@itemdb). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for itemdb.biz is good at 6 characters: "ItemDB". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 153 characters (well-optimized): "ItemDB is a website that brings together information about RuneScape items, including the ID, to help you spend less tim...". 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 page language is declared as en and a favicon is configured. No Open Graph tags are configured. When someone shares a link to itemdb.biz 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 meta keywords tag contains 23 terms including itemdb, item-db, item id list, item list, and itemdatabase. 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with itemdb.biz. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. No tracking IDs were detected on this page that could be used for cross-domain matching.