Skip to content
https://www.colacem.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
6 PASS 10 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 27 ms lookup
REVIEW
1 A records, 27 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 94.188.237.65
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: 2dbffd9669ed414c99519c25ce025227.v1.radwarecloud.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 27 ms
Got: 27 ms
A94.188.237.65
AAAA—
CNAME2dbffd9669ed414c99519c25ce025227.v1.radwarecloud.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 27 ms

Multiple A records provide failover if one server goes down.

Why this matters

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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 94.188.237.65 does not match any cert SAN: 237.188.94-binat-smaug.in-addr.arpa
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 79ms across 3 resolvers (spread 108ms)
REVIEW
Mean 79ms across 3 resolvers (spread 108ms)
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Quad9: 98ms
Got: 98ms via 9.9.9.9:53
Info::
Cloudflare: 124ms
Got: 124ms via 1.1.1.1:53
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
90 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

90
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A
Redirect Chain
1 redirect(s), 289 ms total
PASS
1 redirect(s), 289 ms total
Info::
Single redirect
Got: https://www.colacem.com → https://www.colacem.com/es/es (301)

https://www.colacem.com

157 ms · HTTP/1.1

301

https://www.colacem.com/es/es

132 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.colacem.com301157 msHTTP/1.1
2https://www.colacem.com/es/es200132 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 151 URLs
PASS
robots.txt present, sitemap with 151 URLs
Info::
robots.txt is present
Got: 601 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 151 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 601 B Sitemaps referenced 11 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow:

 
sitemap: https://www.colacem.com/ww/en/sitemap.xml

sitemap: https://www.colacem.com/it/it/sitemap.xml

sitemap: https://www.colacem.com/it/en/sitemap.xml

sitemap: https://www.colacem.com/al/sq/sitemap.xml

sitemap: https://www.colacem.com/al/en/sitemap.xml

sitemap: https://www.colacem.com/es/es/sitemap.xml

sitemap: https://www.colacem.com/es/en/sitemap.xml

sitemap: https://www.colacem.com/do/en/sitemap.xml

sitemap: https://www.colacem.com/do/es/sitemap.xml

sitemap: https://www.colacem.com/tn/fr/sitemap.xml

sitemap: https://www.colacem.com/tn/en/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 151 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.colacem.com/
404https://colacem.com/

HTTP → HTTPS

301http://www.colacem.com/ → https://www.colacem.com/

Consistent

A
Domain Intelligence
colacem.com — via COREhub, S.R.L., 27 years, 3 months old, hosted on Internet_Binat - Internet Binat Ltd, IL
PASS
colacem.com — via COREhub, S.R.L., 27 years, 3 months old, hosted on Internet_Binat - Internet Binat Ltd, IL
Warning::
Domain expires in 40 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Nov 17, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: COREhub, S.R.L.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Internet_Binat - Internet Binat Ltd, IL
Got: AS25003
Domain expiry

29 days

November 17, 2026

SSL certificate

90 days

Issued by DigiCert Inc

Domain age

27 years, 3 months

Registered November 17, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Internet_Binat - Internet Binat Ltd, IL

ASN AS25003

94.188.237.65

Registrar

COREhub, S.R.L.

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar COREhub, S.R.L.
Created November 17, 1999 (27 years, 3 months ago)
Expires November 17, 2026 (1 months)
Last Updated November 18, 2025
Name Servers dns1.financo.it, dns9.interbusiness.it, mailrelay.financo.it
DNSSEC Not enabled
Hosting
IP Address 94.188.237.65
ASN AS25003 (Internet_Binat - Internet Binat Ltd, IL)
Provider Internet_Binat - Internet Binat Ltd, IL
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 217 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
106 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
217 ms
Total Time Total request time from DNS lookup through full response.
217 ms

Connection waterfall

DNS Lookup 106 ms TCP Connect 25 ms TLS Handshake 31 ms Server Processing 55 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback