ja.ingham.org Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of ja.ingham.org on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 2324ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 42 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 65/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Strict-Transport-Security (HSTS) 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 5 technologies across 5 categories powering ja.ingham.org. The detected stack includes Bootstrap, Google Analytics 4, StackPath, jQuery, and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ja.ingham.org receives an overall trust score of 63/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time2324ms
ProtocolHTTP/2
Page Size42 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests170
3rd Party Domains14
Redirect1 hop(s)
Detected Technologies (5)
🎨 Bootstrap
📊 Google Analytics 4
☁️ StackPath
📦 jQuery
🎯 Font Awesome
Security Headers
✓
Content-Security-Policy
Set ✓
✗
Strict-Transport-Security (HSTS)
Not set
✓
X-Content-Type-Options
Set ✓
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=ingham.org
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
ja.ingham.org Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, ja.ingham.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.
Areas of concern include: 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 ja.ingham.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.
Trust Signals
✅ Valid HTTPS
⚠️ DNSSEC not enabled
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
ja.ingham.org Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned ja.ingham.org and identified 5 distinct technologies across 5 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 — provides the styling and responsive layout system for ja.ingham.org.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for ja.ingham.org.
CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for ja.ingham.org.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for ja.ingham.org.
Icon Set: Font Awesome — provides additional functionality for ja.ingham.org.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-T16E8B7XNQ. These IDs can be used to identify other websites operated by the same organization.
CSS Framework
Analytics
📊 Google Analytics 4(95%)
CDN
JavaScript Library
Icon Set
Tracking IDs
ja.ingham.org Performance, Speed & Core Web Vitals
🤖 AI Summary
ja.ingham.org delivers its homepage in 2324ms (server response time), which is considered slow by industry standards. The total page weight is 42 KB, and we detected 170 resource requests loading assets from 14 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 6 CSS files and 6 out of 13 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 ja.ingham.org produces approximately 0.02g 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 42 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ja.ingham.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.02g
RatingA
Page Weight & Optimization
HTML Size42 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests170
3rd Party Domains14
CSS Minified2/6
JS Minified6/13
ja.ingham.org DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
ja.ingham.org resolves to the IPv4 address 104.18.16.13 and also supports IPv6 (2606:4700::6812:110d), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured.
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 ja.ingham.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.
Email & Authentication
MX Provider—
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportYes ✓
ja.ingham.org Page Content, Images & Accessibility
🤖 AI Summary
The homepage of ja.ingham.org contains 702 words of visible text content. This is a moderate amount of content. The page is structured with 2 H2 headings, 4 H3 headings, 0 H4 headings, 1 H5, and 1 H6 headings.
The page includes 3 images. 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 130 internal links pointing to other pages on the same domain and 12 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 13 external JavaScript files, 6 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.
The website has social media presence across 1 platforms: Twitter (@home). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1Ingham County
H2 Tags2
H3 Tags4
H4 Tags0
H5 Tags1
H6 Tags1
Internal Links130
External Links12
Assets & Features
JavaScript Files13
JS Minified6/13
CSS Files6
CSS Minified2/6
Iframes0
Images3
Missing Alt0
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
ja.ingham.org SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for ja.ingham.org is well-optimized at 35 characters: "Ingham County - Jury Administration". 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 ja.ingham.org. 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, the meta robots directive is set to index, follow, and a favicon is configured.
No Open Graph tags are configured. When someone shares a link to ja.ingham.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.
Google SERP Preview
Ingham County - Jury Administration
https://ja.ingham.org
Meta Tags
TitleIngham County - Jury Administration...
Title Length35 chars
Meta Desc Length0 chars
H1Ingham County
Languageen
Canonical—
Meta Robotsindex, follow
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconSet ✓
ja.ingham.org Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with ja.ingham.org. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-T16E8B7XNQ.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)