amusaveba.org

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, amusaveba.org receives a trust score of 62/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 and HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks. 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 amusaveba.org 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 technology detection engine scanned amusaveba.org and identified 5 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: Wix — manages the content and page structure for amusaveba.org. UI Library: React (version 18.3.1) — handles the user interface rendering and component management for amusaveba.org. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for amusaveba.org. Monitoring: Sentry — monitors application performance and errors for amusaveba.org. JavaScript Library: Lodash — provides utility functions and DOM manipulation for amusaveba.org.

🤖 AI Summary

amusaveba.org delivers its homepage in 4669ms (server response time), which is considered slow by industry standards. The total page weight is 558 KB, and we detected 80 resource requests loading assets from 6 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 0 CSS files and 8 out of 11 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 amusaveba.org produces approximately 0.27g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 558 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for amusaveba.org. 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

amusaveba.org resolves to the IPv4 address 185.230.63.186, 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 3 A record(s) configured. The domain name system is managed by 2 name servers: ns0.wixdns.net and ns1.wixdns.net. 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 amusaveba.org is handled by amusaveba.org with 1 MX records configured: mail.amusaveba.org. 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 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 amusaveba.org. 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. Our subdomain enumeration scan discovered 3 active subdomains for amusaveba.org: m.amusaveba.org, mail.amusaveba.org, and www.amusaveba.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of amusaveba.org contains 376 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 15 H4 headings, 1 H5, and 1 H6 headings. The page includes 5 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 34 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 11 external JavaScript files, 0 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 Schema.org structured data (WebSite). Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: Twitter (@bolt-performance). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for amusaveba.org is good at 69 characters: "Cleveland-Cliffs Steel LLC VEBA Trust formerly ArcelorMittal USA VEBA". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 156 characters (acceptable): "The VEBA was established to assist the retirees who were directly affected by the bankruptcies of LTV Steel • ACME, Beth...". 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://www.amusaveba.org, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Cleveland-Cliffs Steel LLC VEBA Trust formerly ArcelorMittal..."), 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. 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: 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.

🤖 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 amusaveba.org. 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.