sedsucre.gov.co

We performed a comprehensive analysis of sedsucre.gov.co on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 26530ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 8 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 3 technologies across 3 categories powering sedsucre.gov.co. The detected stack includes Matomo, hCaptcha, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, sedsucre.gov.co receives an overall trust score of 62/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, sedsucre.gov.co 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 sedsucre.gov.co 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 sedsucre.gov.co 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. Analytics: Matomo — tracks visitor behavior and provides traffic insights for sedsucre.gov.co. Security: hCaptcha — provides security features like bot detection and CAPTCHA for sedsucre.gov.co. Icon Set: Font Awesome — provides additional functionality for sedsucre.gov.co.

sedsucre.gov.co resolves to the IPv4 address 20.88.170.7 and also supports IPv6 (2603:1030:20c:9::114), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 4 name servers: az-acadcpr30.mcdmintic.local, az-acadcpr31.mcdmintic.local, ns3.mintic.gov.co, and ns4.mintic.gov.co. 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. 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 sedsucre.gov.co. 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 1 active subdomains for sedsucre.gov.co: www.sedsucre.gov.co. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for sedsucre.gov.co is well-optimized at 37 characters: "Secretaría de Educación Departamental". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 47 characters (acceptable): "Secretaría de Educación Departamental de Sucre ". 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 es-es and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Secretaría de Educación Departamental..."), OG description, 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. A Twitter Card of type summary is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.