michigan.bank

We performed a comprehensive analysis of michigan.bank on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 4382ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 85 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 ECDSA-SHA384 signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-08-28, which is 56 days from now. 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-Frame-Options, and X-Content-Type-Options. However, the site is missing 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 3 technologies across 3 categories powering michigan.bank. The detected stack includes Bootstrap 50, Google Analytics 4, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, michigan.bank receives an overall trust score of 84/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, michigan.bank receives a trust score of 84/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 56 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses. Areas of concern include: missing Referrer-Policy, potentially leaking URL information to third parties 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 michigan.bank 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 michigan.bank and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CSS Framework: Bootstrap (version 50) — provides the styling and responsive layout system for michigan.bank. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for michigan.bank. JavaScript Library: jQuery — provides utility functions and DOM manipulation for michigan.bank. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-5KTM2JL0FS. These IDs can be used to identify other websites operated by the same organization.

michigan.bank delivers its homepage in 4382ms (server response time), which is considered slow by industry standards. The total page weight is 85 KB, and we detected 101 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: 0 out of 5 CSS files and 4 out of 10 JavaScript files are minified. Minifying the remaining 11 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 michigan.bank produces approximately 0.04g 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 85 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for michigan.bank. 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.

michigan.bank resolves to the IPv4 address 104.16.130.63, 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 2 name servers: ns1.encircadns.bank and ns2.encircadns.bank. 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 michigan.bank is handled by sophos.com with 2 MX records configured: mx-02-us-east-2.prod.hydra.sophos.com and mx-01-us-east-2.prod.hydra.sophos.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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for michigan.bank, 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 michigan.bank contains 199 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 4 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 21 images. 14 images (67%) 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 33% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 41 internal links pointing to other pages on the same domain and 22 external links pointing to third-party websites. There are 10 external JavaScript files, 5 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: Facebook (@mibankers). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for michigan.bank 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 michigan.bank. 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://michigan.bank/mibankers/mibankers/default.aspx, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. 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.