Skip to content
https://meduza.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
6
INFO
1
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 75 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 75 B Sitemaps referenced 0 User-agents Twitterbot, * Blocking No — crawling allowed
User-agent: Twitterbot

User-agent: *
Disallow: /insite/
Disallow: /embed/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
2 A records, 30 ms lookup
PASS
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.1.79, 104.18.0.79
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:14f, 2606:4700::6812:4f
Info::
2 nameserver(s) configured
Got: tom.ns.cloudflare.com, maria.ns.cloudflare.com
Info::
5 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: 30 ms
Got: 30 ms
A104.18.1.79, 104.18.0.79
AAAA2606:4700::6812:14f, 2606:4700::6812:4f
CNAME
NStom.ns.cloudflare.com, maria.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
yandex-verification: 247631b60b26626a
google-site-verification=zl9NktFGCkCrxBAMlmOsDzFVaoZt1zlPAeTP57ji7J4
google-site-verification=_IQIZrvM80fLitmG2bl_rxsneUqEXvXEwmku4orOSI0
google-site-verification=iR2lmXENHyKal8NHqmS5IlaQ6yBCSOSmKMQ8_qYnfJ4
mailru-verification: af14799471b9f946
firebase=meduza-flutter
apple-domain-verification=9WrUlTz6viEWpzCi
SPF v=spf1 include:spf0.meduza.io -all
facebook-domain-verification=oy14jw4lf4va7ny1oby3u57hnhn03t
CAALookup not available with standard resolver
Resolved in 30 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://meduza.io

https://meduza.io

75 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://meduza.io20075 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:14f, 2606:4700::6812:4f
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:14f, 2606:4700::6812:4f Connection Reachable (17 ms)
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.meduza.io/
200https://meduza.io/

Preferred variant: non-www

HTTP → HTTPS

308http://meduza.io/ https://meduza.io/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 41 ms Content Transfer 17 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f075f4dbce5da89-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f075f4dbce5da89-CDG
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