Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BRedirect Chain1 redirect(s), 1987 ms totalREVIEW
https://cepal.org
1637 ms · HTTP/1.1
https://www.cepal.org/
350 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cepal.org | 301 | 1637 ms | HTTP/1.1 | |
| 2 | https://www.cepal.org/ | 200 | 350 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CHTTP Probe TimingActionTotal 1693 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations31 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records1 A records, 340 ms lookupPASS
| A | 151.101.222.133 |
| AAAA | — |
| CNAME | — |
| NS | ns2.gtdinternet.com, ns.gtdinternet.com, ens.cepal.org |
| MX | 10 cepal-org.mail.protection.outlook.com |
| TXT | _amazonses.cepal.org:0PbkcPs87kmEdOT6pRsN+TV16g9Q3Qwn2fNm7hTzcXM= _globalsign-domain-verification=ZYDfOQ85WwAgpgqTL9HZr9Y54WwhttOjKWh2eky-8a google-site-verification=bnE5Z5RzPhgt7Tea7xV-R0UJXNm9Jo3u_sRDVKsoS9g SPF v=spf1 a mx include:un.org include:spf-eu.exlibrisgroup.com -all amazonses:0PbkcPs87kmEdOT6pRsN+TV16g9Q3Qwn2fNm7hTzcXM= MS=ms21087918 _globalsign-domain-verification=GDoXjhrrDz8-hBV_4ElwtuuWwmYiJRckr0G8EZtfHl |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ACrawlabilityno robots.txt, sitemap with 1 URLsPASS
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
A+Domain Intelligencecepal.org — via Network Solutions, LLC, 29 years old, hosted on FastlyPASS
452 days
September 11, 2027
31 days
Issued by Let's Encrypt
29 years
Registered September 12, 1997
Not enabled
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.222.133
Network Solutions, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice