myccc.coconino.edu Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of myccc.coconino.edu on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 21312ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 29 KB.
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 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, 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 6 technologies across 5 categories powering myccc.coconino.edu. The detected stack includes Angular, Bootstrap, Cloudflare, StackPath, jQuery, and Font Awesome. The site uses Angular as its primary framework.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, myccc.coconino.edu receives an overall trust score of 62/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time21312ms
ProtocolHTTP/2
Page Size29 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerWSO2 Carbon Server
Total Requests38
3rd Party Domains6
Redirect4 hop(s)
Detected Technologies (6)
🔧 Angular
🎨 Bootstrap
☁️ Cloudflare
☁️ StackPath
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerInternet2
Issuer FullcountryName=US, organizationName=Internet2, commonName=InCommon RSA Server CA 2
SubjectcountryName=US, stateOrProvinceName=Arizona, organizationName=Coconino Community College, commonName=*.coconino.edu
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
myccc.coconino.edu Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, myccc.coconino.edu receives a trust score of 62/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 and HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks.
Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 myccc.coconino.edu 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
✅ HSTS enabled
⚠️ DNSSEC not enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
myccc.coconino.edu Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned myccc.coconino.edu and identified 6 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.
Framework: Angular — provides the application framework and routing for myccc.coconino.edu.
CSS Framework: Bootstrap — provides the styling and responsive layout system for myccc.coconino.edu.
CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for myccc.coconino.edu.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for myccc.coconino.edu.
Icon Set: Font Awesome — provides additional functionality for myccc.coconino.edu.
Framework
CSS Framework
CDN
☁️ Cloudflare(95%)☁️ StackPath(95%)
JavaScript Library
Icon Set
myccc.coconino.edu Performance, Speed & Core Web Vitals
🤖 AI Summary
myccc.coconino.edu delivers its homepage in 21312ms (server response time), which is considered slow by industry standards. The total page weight is 29 KB, and we detected 38 resource requests loading assets from 6 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 7 CSS files and 7 out of 18 JavaScript files are minified. Minifying the remaining 16 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.
From an environmental perspective, each page view of myccc.coconino.edu produces approximately 0.01g 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 29 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for myccc.coconino.edu. 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.01g
RatingA
Page Weight & Optimization
HTML Size29 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests38
3rd Party Domains6
CSS Minified2/7
JS Minified7/18
myccc.coconino.edu DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
myccc.coconino.edu resolves to the IPv4 address 52.43.16.48, 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 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 myccc.coconino.edu. 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 SupportNo
myccc.coconino.edu Page Content, Images & Accessibility
🤖 AI Summary
The homepage of myccc.coconino.edu contains 68 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 1 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 6 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 18 external JavaScript files, 7 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.
Content Structure
H1Identity Server
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links6
External Links1
Assets & Features
JavaScript Files18
JS Minified7/18
CSS Files7
CSS Minified2/7
Iframes0
Images1
Missing Alt0
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
myccc.coconino.edu SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
No meta description is configured for myccc.coconino.edu. 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 the meta robots directive is set to noindex.
No Open Graph tags are configured. When someone shares a link to myccc.coconino.edu 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.
Meta Tags
Title—...
Title Length0 chars
Meta Desc Length0 chars
H1Identity Server
Languageen
Canonical—
Meta Robotsnoindex
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconNot set