tcoe.instructure.com

We performed a comprehensive analysis of tcoe.instructure.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 1098ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 24 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 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing X-Frame-Options 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 4 technologies across 4 categories powering tcoe.instructure.com. The detected stack includes React, Webpack, reCAPTCHA v3, and Amazon CloudFront. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, tcoe.instructure.com receives an overall trust score of 67/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, tcoe.instructure.com receives a trust score of 67/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: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 tcoe.instructure.com 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 tcoe.instructure.com and identified 4 distinct technologies across 4 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 tcoe.instructure.com. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for tcoe.instructure.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for tcoe.instructure.com. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for tcoe.instructure.com.

tcoe.instructure.com resolves to the IPv4 address 18.165.122.94, 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 4 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 tcoe.instructure.com. 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. Our subdomain enumeration scan discovered 25 active subdomains for tcoe.instructure.com: admin.tcoe.instructure.com, api.tcoe.instructure.com, app.tcoe.instructure.com, apps.tcoe.instructure.com, blog.tcoe.instructure.com, cdn.tcoe.instructure.com, community.tcoe.instructure.com, and dev.tcoe.instructure.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for tcoe.instructure.com is good at 26 characters: "Canvas Login | Instructure". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 139 characters (well-optimized): "Official Login page for Canvas student login, School Search Canvas, Canvas Network, Canvas Community, and Canvas Free Fo...". 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 page language is declared as en, the meta robots directive is set to noindex,nofollow, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to tcoe.instructure.com 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.