metalradar.com

We performed a comprehensive analysis of metalradar.com on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 28330ms. 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 1113 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-07, which is 68 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 4 technologies across 3 categories powering metalradar.com. The detected stack includes Next.js css, React, Webpack, and Vite. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, metalradar.com receives an overall trust score of 68/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, metalradar.com 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 Amazon with 68 days until expiration, DMARC email authentication with a quarantine policy, and a well-established domain registered for over 19.4 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 metalradar.com 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. The domain is registered through Amazon Registrar, Inc. based in FI, with a registration date of 2007-02-14 and expiration date of 2027-02-14.

Our technology detection engine scanned metalradar.com and identified 4 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version css) — provides the application framework and routing for metalradar.com. UI Library: React — handles the user interface rendering and component management for metalradar.com. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for metalradar.com.

metalradar.com delivers its homepage in 28330ms (server response time), which is considered slow by industry standards. The total page weight is 1113 KB, and we detected 130 resource requests loading assets from 0 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 metalradar.com. 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: 0 out of 11 CSS files and 0 out of 16 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. 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 metalradar.com produces approximately 0.54g of CO₂, earning a carbon rating of D. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 1113 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for metalradar.com. 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.

metalradar.com resolves to the IPv4 address 18.165.140.104 and also supports IPv6 (2600:9000:25f7:a200:5:5f22:6200:93a1), demonstrating modern network infrastructure readiness. The domain has 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1214.awsdns-23.org, ns-1678.awsdns-17.co.uk, ns-487.awsdns-60.com, and ns-532.awsdns-02.net. 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. Email for metalradar.com is handled by Microsoft 365 with 1 MX records configured: metalradar-com.mail.protection.outlook.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 metalradar.com. 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 domain is registered through Amazon Registrar, Inc. (FI). It was first registered on 2007-02-14 and is set to expire on 2027-02-14, making it 19.4 years old. Our subdomain enumeration scan discovered 9 active subdomains for metalradar.com: admin.metalradar.com, api.metalradar.com, app.metalradar.com, blog.metalradar.com, cdn.metalradar.com, dev.metalradar.com, m.metalradar.com, and shop.metalradar.com. Plus 1 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of metalradar.com contains 462 words of visible text content. This is a moderate amount of content. The page is structured with 8 H2 headings, 3 H3 headings, 0 H4 headings. The page includes 30 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 55 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 16 external JavaScript files, 11 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) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on metalradar.com: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for metalradar.com is well-optimized at 34 characters: "real-time metal data - Metal Radar". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 20 characters (acceptable): " for scrap recyclers". 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://metalradar.com/home, preventing duplicate content issues and the page language is declared as en. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("real-time metal data..."), OG description, 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.