Skip to content
https://diagrams.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
76 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0836a2caf66fc6-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0836a2caf66fc6-CDG
A+
DNS Records
2 A records, 39 ms lookup
PASS
2 A records, 39 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.4.247, 104.18.5.247
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:5f7, 2606:4700::6812:4f7
Info::
2 nameserver(s) configured
Got: amy.ns.cloudflare.com, phil.ns.cloudflare.com
Info::
2 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: 39 ms
Got: 39 ms
A104.18.4.247, 104.18.5.247
AAAA2606:4700::6812:5f7, 2606:4700::6812:4f7
CNAME—
NSamy.ns.cloudflare.com, phil.ns.cloudflare.com
MX
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
TXT
MS=ms91891564
google-site-verification=yST7_lVIrubgcMmpbJrW2rRshn3QN-ZBPNiTcFp_ERQ
google-site-verification=POrDKMR9wpHLbywZ625o5Boq15SGrNVMzPNi0eC0D2U
SPF v=spf1 include:spf.messagingengine.com include:_spf.atlassian.net -all
l6s19nlccejdfnhlc8grbg82rk
fm42ebuifj826o5mjn54c6nmkg
CAALookup not available with standard resolver
Resolved in 39 ms

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), 194 ms total
PASS
1 redirect(s), 194 ms total
Info::
Single redirect
Got: https://diagrams.net → https://www.drawio.com/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://diagrams.net

58 ms · HTTP/1.1

301

https://www.drawio.com/

136 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://diagrams.net30158 msHTTP/1.1cloudflare
2https://www.drawio.com/200136 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:5f7, 2606:4700::6812:4f7
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:5f7, 2606:4700::6812:4f7 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 580 URLs
PASS
robots.txt present, sitemap with 580 URLs
Info::
robots.txt is present
Got: 44 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 580 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 44 B Sitemaps referenced 1 User-agents Blocking No — crawling allowed
Sitemap: https://www.drawio.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 580 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.diagrams.net/
200https://diagrams.net/

Preferred variant: non-www

HTTP → HTTPS

301http://diagrams.net/ → https://diagrams.net/

Consistent

A+
Domain Intelligence
diagrams.net — via Cloudflare, Inc., 16 years, 4 months old
PASS
diagrams.net — via Cloudflare, Inc., 16 years, 4 months old
Info::
Domain registered until Mar 17, 2030 (3 years, 11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, Inc.
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.
Domain expiry

1373 days

March 17, 2030

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

16 years, 4 months

Registered March 17, 2010

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:5f7

Registrar

Cloudflare, Inc.

Unlocked 2 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 Cloudflare, Inc.
Created March 17, 2010 (16 years, 4 months ago)
Expires March 17, 2030 (3 years, 11 months)
Last Updated December 1, 2021
Name Servers amy.ns.cloudflare.com, phil.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700::6812:5f7
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 19 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