lansingmi.gov

We performed a comprehensive analysis of lansingmi.gov on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 16725ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 429 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 Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-08-05, which is 29 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-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 6 technologies across 6 categories powering lansingmi.gov. The detected stack includes Angular, React, Vite, Google Analytics 4, Google Tag Manager, and Google Fonts. The site uses Angular as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, lansingmi.gov receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, lansingmi.gov receives a trust score of 80/100, which places it in the "Very 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, a valid SSL certificate issued by Let's Encrypt with 29 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked lansingmi.gov 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 lansingmi.gov and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Angular — provides the application framework and routing for lansingmi.gov. UI Library: React — handles the user interface rendering and component management for lansingmi.gov. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for lansingmi.gov. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for lansingmi.gov. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for lansingmi.gov. Fonts: Google Fonts — delivers web fonts for typography for lansingmi.gov. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-ZSYLT7EQ8K and Google Tag Manager container GTM-TBF9ZQ8. These IDs can be used to identify other websites operated by the same organization.

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

lansingmi.gov resolves to the IPv4 address 20.114.211.29, 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 1 A record(s) configured. The domain name system is managed by 4 name servers: dns1.p10.nsone.net, dns2.p10.nsone.net, dns3.p10.nsone.net, and dns4.p10.nsone.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 lansingmi.gov is handled by pphosted.com with 2 MX records configured: mxa-001ef302.gslb.pphosted.com and mxb-001ef302.gslb.pphosted.com. 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 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 enabled for lansingmi.gov, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.

The homepage of lansingmi.gov contains 44 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 1 image. 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 13 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 6 external JavaScript files, 5 CSS stylesheets, and 2 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.

The title tag for lansingmi.gov is well-optimized at 49 characters: "Lansing, MI - Official Website | Official Website". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for lansingmi.gov. 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 page language is declared as en and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Home..."), 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. The meta keywords tag contains 1 terms including Home. 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.