Skip to content
https://unicen.edu.ar

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
10
PASS
6
INFO
1
Probed from New York, United Stated
200 OK
Checks
17
6 PASS 10 REVIEW
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.
C
Reverse DNS
Action
0/3 IPs match cert SAN
REVIEW
0/3 IPs match cert SAN
Info::
PTR lookup failed for 131.221.0.52: lookup 131.221.0.52: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 131.221.0.53: lookup 131.221.0.53: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 131.221.0.54: lookup 131.221.0.54: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Multi-Resolver DNS Speed
Mean 106ms across 3 resolvers (spread 155ms)
REVIEW
Mean 106ms across 3 resolvers (spread 155ms)
Info::
Google: 8ms
Got: 8ms via 8.8.8.8:53
Info::
Quad9: 148ms
Got: 148ms via 9.9.9.9:53
Info::
Cloudflare: 163ms
Got: 163ms 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
HTTP Probe Timing
Total 1312 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
170 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
162 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
168 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
989 ms
Total Time Total request time from DNS lookup through full response.
1.31 s

Connection waterfall

DNS Lookup 170 ms TCP Connect 162 ms TLS Handshake 168 ms Server Processing 489 ms Content Transfer 324 ms
B
TLS Certificate Expiry & Recommendations
53 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

53
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
C
CDN & Delivery
Action
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 4 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a504c6b3f83f729f-EWR
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache BYPASS
Got: cf-ray: a504c6b3f83f729f-EWR
Info::
Assets on Cloudflare: cdn.jsdelivr.net (assets: 3), cache HIT
Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: BYPASS
  • cdn.jsdelivr.net — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • img.youtube.com — assets: 7 · Google
  • www.youtube.com — assets: 2 · below probe threshold
  • cdn.gtranslate.net — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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
DNS Records
3 A records, 322 ms lookup
PASS
3 A records, 322 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 131.221.0.52, 131.221.0.53, 131.221.0.54
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns-1.unicen.edu.ar, ns-2.unicen.edu.ar, ns-3.unicen.edu.ar
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (322 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 322 ms
A131.221.0.52, 131.221.0.53, 131.221.0.54
AAAA—
CNAME—
NSns-1.unicen.edu.ar, ns-2.unicen.edu.ar, ns-3.unicen.edu.ar
MX
10 mx-1.unicen.edu.ar
10 mx-2.unicen.edu.ar
TXT
MS=ms85199664
SPF v=spf1 mx include:_spf.google.com include:_spf.unicen.edu.ar -all
google-site-verification=wbiU7_haoMEpIjATryIMurpODHljqSRH1g5sroc8WSs
CAALookup not available with standard resolver
Resolved in 322 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://unicen.edu.ar

https://unicen.edu.ar

789 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unicen.edu.ar200789 msHTTP/1.1Apache/2.4.69 (Debian)
A+
Crawlability
robots.txt present, sitemap with 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 114 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
Sitemap index with 18 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 114 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://unicen.edu.ar/wp-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 18 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.unicen.edu.ar/
200https://unicen.edu.ar/

Preferred variant: non-www

HTTP → HTTPS

301http://unicen.edu.ar/ → https://unicen.edu.ar/

Consistent

Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback