michiganpublic.org

We performed a comprehensive analysis of michiganpublic.org on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 8672ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 302 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 Internet2 (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-10-21, which is 113 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Content-Security-Policy. However, the site is missing Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, 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 9 technologies across 7 categories powering michiganpublic.org. The detected stack includes React, Webpack, Vite, Google Tag Manager, Meta Pixel, Mailchimp, Google Fonts, Adobe Fonts, and jQuery. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, michiganpublic.org receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, michiganpublic.org receives a trust score of 63/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 Internet2 with 113 days until expiration, DMARC email authentication with a none policy, and a domain registered for 3.9 years. Areas of concern include: 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 michiganpublic.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. The domain is registered through Tucows Domains Inc. based in US, with a registration date of 2022-08-12 and expiration date of 2028-08-12.

Our technology detection engine scanned michiganpublic.org and identified 9 distinct technologies across 7 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for michiganpublic.org. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for michiganpublic.org. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for michiganpublic.org. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for michiganpublic.org. Email Marketing: Mailchimp — manages email campaigns and subscriber lists for michiganpublic.org. Fonts: Google Fonts and Adobe Fonts — delivers web fonts for typography for michiganpublic.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for michiganpublic.org. We also extracted the following tracking identifiers: Google Tag Manager container GTM-N39QFDR. These IDs can be used to identify other websites operated by the same organization.

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

michiganpublic.org resolves to the IPv4 address 3.130.223.75, 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 4 name servers: dns1.itd.umich.edu, dns2.itd.umich.edu, dns3.umich.org, and dns4.umich.org. 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 michiganpublic.org is handled by umich.edu with 1 MX records configured: mx1.a.mail.umich.edu. 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 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 michiganpublic.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. The domain is registered through Tucows Domains Inc. (US). It was first registered on 2022-08-12 and is set to expire on 2028-08-12, making it 3.9 years old. Our subdomain enumeration scan discovered 1 active subdomains for michiganpublic.org: www.michiganpublic.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of michiganpublic.org contains 2,016 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 1 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 32 images. 7 images (22%) 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 78% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 351 internal links pointing to other pages on the same domain and 28 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 3 external JavaScript files, 3 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Schema.org structured data (ImageObject, NewsMediaOrganization, SearchAction, and WebSite), and RSS feed for content syndication. The website has social media presence across 5 platforms: Facebook (@michiganpublic), Twitter (@michigan_public), Instagram (@michiganpublic), Linkedin (@michigan-public), and Youtube (@michigan_public). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for michiganpublic.org is good at 15 characters: "Michigan Public". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 156 characters (acceptable): "Your public radio source for NPR and Michigan news, events, politics, arts/culture, environment. Serving Ann Arbor, Detr...". 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.michiganpublic.org/, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to max-image-preview:large, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to michiganpublic.org 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 site implements Schema.org structured data with the following types: ImageObject, NewsMediaOrganization, SearchAction, and 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. The meta keywords tag contains 10 terms including Michigan, Michigan Public Media, Michigan news, Michigan news radio, and detroit michigan radio. 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.