metadata.works

We performed a comprehensive analysis of metadata.works on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 29516ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 102 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 55/100 (moderate). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), and Referrer-Policy. However, the site is missing X-Frame-Options, X-Content-Type-Options, 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 4 categories powering metadata.works. The detected stack includes Google Analytics 4, Google Tag Manager, HubSpot, and Cloudflare. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, metadata.works receives an overall trust score of 62/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, metadata.works 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: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 metadata.works 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 metadata.works and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for metadata.works. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for metadata.works. Marketing: HubSpot — provides marketing automation capabilities for metadata.works. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for metadata.works. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-HCFVNBGRVX and Google Tag Manager container GTM-TZ3RTF9J. These IDs can be used to identify other websites operated by the same organization.

metadata.works delivers its homepage in 29516ms (server response time), which is considered slow by industry standards. The total page weight is 102 KB, and we detected 90 resource requests loading assets from 5 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: 5 out of 6 CSS files and 3 out of 9 JavaScript files are minified. Minifying the remaining 7 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 metadata.works produces approximately 0.05g 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 102 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for metadata.works. 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.

metadata.works resolves to the IPv4 address 16.12.17.4, 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 8 A record(s) configured. The domain name system is managed by 4 name servers: ns-1283.awsdns-32.org, ns-1920.awsdns-48.co.uk, ns-466.awsdns-58.com, and ns-724.awsdns-26.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. 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 metadata.works. 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 metadata.works contains 586 words of visible text content. This is a moderate amount of content. The page is structured with 6 H2 headings, 4 H3 headings, 8 H4 headings. The page includes 25 images. 4 images (16%) 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 84% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 45 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 9 external JavaScript files, 6 CSS stylesheets, and 1 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on metadata.works: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 2 platforms: Twitter (@MetadataW) and Linkedin (@35531176). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for metadata.works is good at 4 characters: "Home". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for metadata.works. 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 canonical url is correctly set to https://metadataworks.ai, preventing duplicate content issues and the page language is declared as en. Open Graph meta tags are configured with 1/4 recommended fields: OG title ("Home..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.