burning-glass.com

We performed a comprehensive analysis of burning-glass.com on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 8444ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 417 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 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing X-Frame-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 burning-glass.com. The detected stack includes Next.js media, React, Microsoft Clarity, and LinkedIn Insight Tag. The site uses Next.js as its primary framework (version media). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, burning-glass.com receives an overall trust score of 73/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, burning-glass.com receives a trust score of 73/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, and DMARC email authentication with a none policy. 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 burning-glass.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.

Our technology detection engine scanned burning-glass.com 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. Framework: Next.js (version media) — provides the application framework and routing for burning-glass.com. UI Library: React — handles the user interface rendering and component management for burning-glass.com. Analytics: Microsoft Clarity — tracks visitor behavior and provides traffic insights for burning-glass.com. Advertising: LinkedIn Insight Tag — handles advertising pixel tracking and conversion measurement for burning-glass.com.

burning-glass.com delivers its homepage in 8444ms (server response time), which is considered slow by industry standards. The total page weight is 417 KB, and we detected 147 resource requests loading assets from 17 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 27 JavaScript files are minified. Minifying the remaining 30 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 burning-glass.com produces approximately 0.2g of CO₂, earning a carbon rating of B. 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 417 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for burning-glass.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.

burning-glass.com resolves to the IPv4 address 54.231.131.221, 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-1235.awsdns-26.org, ns-1762.awsdns-28.co.uk, ns-187.awsdns-23.com, and ns-895.awsdns-47.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 burning-glass.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 burning-glass.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 homepage of burning-glass.com contains 710 words of visible text content. This is a moderate amount of content. The page is structured with 3 H2 headings, 12 H3 headings, 4 H4 headings. The page includes 17 images. 3 images (18%) 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 82% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 43 internal links pointing to other pages on the same domain and 21 external links pointing to third-party websites. There are 27 external JavaScript files, 3 CSS stylesheets, and 0 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 burning-glass.com: Visa, American Express, Discover, and JCB. 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 5 platforms: Facebook (@LightcastData), Twitter (@LightcastData), Instagram (@lightcastdata), Linkedin (@lightcastdata), and Youtube (@lightcastdata). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for burning-glass.com is good at 26 characters: "Burning Glass is Lightcast". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 273 characters (slightly long): "Burning Glass Technologies, and its commitment to innovative solutions and rigorous economic research, live on in Lightc...". 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://lightcast.io/burning-glass-technologies, 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 ("Burning Glass is Lightcast..."), 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.