Skip to content
https://cnr.it

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

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

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2189 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2189 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.cnr.it/
200https://cnr.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://cnr.it/ https://www.cnr.it//

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
1 A records, 63 ms lookup
PASS
1 A records, 63 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.146.205.11
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns.ge.cnr.it, dns2.cnr.it, nameserver.cnr.it, dns.cnr.it
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 63 ms
Got: 63 ms
A150.146.205.11
AAAA
CNAME
NSns.ge.cnr.it, dns2.cnr.it, nameserver.cnr.it, dns.cnr.it
MX
10 cnr-it.mail.protection.outlook.com
TXT
6f4a51bb3c944ff9bdc3a7b5bcda8cc7
OSSRH-49564
actalis-dcv=jfujv5vhde0f8fkf8iv5kfi7g4
HARICA-I2A9TTPNoQZiaLHBfHg
SPF v=spf1 ip4:150.146.0.0/16 ip4:130.186.31.160/27 a:cnr.it include:spf.protection....
MS=ms89640468
apple-domain-verification=YH7epoO0xtkr3iR7
HARICA-7zyiVpcjc962SJm5QkL
CAALookup not available with standard resolver
Resolved in 63 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 340 ms total
PASS
1 redirect(s), 340 ms total
Info::
Single redirect
Got: https://cnr.it → https://www.cnr.it// (301)
Info::
WWW normalization redirect

https://cnr.it

151 ms · HTTP/1.1

301

https://www.cnr.it//

189 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cnr.it301151 msHTTP/1.1Apache
2https://www.cnr.it//200189 msHTTP/1.1nginx/1.18.0

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
cnr.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT
PASS
cnr.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT
Info::
Domain registered until Jan 29, 2027 (9 months remaining)
Info::
Registrar: GARR-REG
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: ASGARR Consortium GARR, IT
Got: AS137
Domain expiry

227 days

January 29, 2027

SSL certificate

213 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

30 years, 8 months

Registered January 29, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ASGARR Consortium GARR, IT

ASN AS137

150.146.205.11

Registrar

GARR-REG

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GARR-REG
Created January 29, 1996 (30 years, 8 months ago)
Expires January 29, 2027 (9 months)
Last Updated February 14, 2026
Name Servers ns.ge.cnr.it, nameserver.cnr.it, dns.cnr.it, dns2.cnr.it
Registrant Consiglio Nazionale delle Ricerche
Hosting
IP Address 150.146.205.11
ASN AS137 (ASGARR Consortium GARR, IT)
Provider ASGARR Consortium GARR, IT
Data source: whois (0.7s)

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 195 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
35 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
78 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
196 ms
Total Time Total request time from DNS lookup through full response.
196 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 35 ms TLS Handshake 78 ms Server Processing 35 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