Skip to content
https://mjt.lu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 2 REVIEW 3 FIX
D
Crawlability
Action
robots.txt present, sitemap with 0 URLs
FIX
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 25 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 25 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.mjt.lu/
200https://mjt.lu/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://mjt.lu/

HTTP version does not redirect to HTTPS

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
TLS Certificate Expiry & Recommendations
131 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

131
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
A+
DNS Records
1 A records, 46 ms lookup
PASS
1 A records, 46 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.241.186.140
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.mljt.tech, ns0.mljt.tech, ns1.mljt.tech
Info::
7 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: 46 ms
Got: 46 ms
A35.241.186.140
AAAA—
CNAME—
NSns2.mljt.tech, ns0.mljt.tech, ns1.mljt.tech
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx5.googlemail.com
10 aspmx3.googlemail.com
10 aspmx4.googlemail.com
TXT
xj1wydsz4qng3qh6f6cs1wrfjt4r6j25
kyfdvsxw7p728rsftf91w3mmjc8ngxm2
SPF v=spf1 -all
google-site-verification=lii1iMgXhtCTprO_aRPsu1EWN2O0IfKbHB-fYuwdKeQ
google-site-verification=tmbTfXzk1Zuks5Sye6fMrDPbQIgmbWwmqVi6JP2aI30
_lovoivo9hsiy950ihfm8uptjsx8f9t7
CAALookup not available with standard resolver
Resolved in 46 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mjt.lu

https://mjt.lu

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mjt.lu20085 msHTTP/1.1
A+
Domain Intelligence
mjt.lu — via OVH, hosted on Google Cloud
PASS
mjt.lu — via OVH, hosted on Google Cloud
Info::
Registrar: OVH
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

Unknown

SSL certificate

131 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

35.241.186.140

Registrar

OVH

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar OVH
Name Servers ns1.mljt.tech, ns0.mljt.tech, ns2.mljt.tech
Hosting
IP Address 35.241.186.140
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (1.7s)
A+
HTTP Probe Timing
Total 116 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
26 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
32 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
117 ms
Total Time Total request time from DNS lookup through full response.
117 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 26 ms TLS Handshake 32 ms Server Processing 27 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