Skip to content
https://esa.int

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
3 PASS 5 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: 1042 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 1042 B Sitemaps referenced 0 User-agents YandexCalendar, YahooCacheSystem, YandexMedia, YaDirectFetcher, YandexNews, YandexMarket, YandexImages, *, Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp), YandexBot, bingbot, YandexCatalog, YandexBlogs, YandexPagechecker, YandexMetrika Blocking No — crawling allowed
User-agent: *
Crawl-delay: 1
Allow: /
Disallow: /spaceinvideos/layout/set
Disallow: /spaceinimages/layout/set
Disallow: /esatv/layout/set
Disallow: /layout/set
Disallow: /*/layout/set
Disallow: /ger/layout/set
Disallow: /fre/layout/set
Disallow: /dut/layout/set
Disallow: /dan/layout/set
Disallow: /esl/layout/set
Disallow: /fin/layout/set
Disallow: /ell/layout/set
Disallow: /ita/layout/set
Disallow: /nor/layout/set
Disallow: /pol/layout/set
Disallow: /por/layout/set
Disallow: /cze/layout/set
Disallow: /ron/layout/set
Disallow: /swe/layout/set
Disallow: /esearch

User-agent: YahooCacheSystem
User-agent: Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)
Crawl-delay: 1

User-agent: YandexBot
User-agent: YandexMedia
User-agent: YandexImages
User-agent: YandexCatalog
User-agent: YaDirectFetcher
User-agent: YandexBlogs
User-agent: YandexNews
User-agent: YandexPagechecker
User-agent: YandexMetrika
User-agent: YandexMarket
User-agent: YandexCalendar
Crawl-delay: 2

User-agent: bingbot
Crawl-delay: 1



sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.esa.int/
200https://esa.int/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://esa.int/ https://esa.int/

Consistent

B
HTTP Probe Timing
Total 821 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
211 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
202 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
206 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
821 ms
Total Time Total request time from DNS lookup through full response.
821 ms

Connection waterfall

DNS Lookup 211 ms TCP Connect 202 ms TLS Handshake 206 ms Server Processing 202 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
197 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

197
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, 221 ms lookup
PASS
1 A records, 221 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 178.32.232.86
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: ns4.esa.int, ns1.esa.int, ns2.esa.int, ns3.esa.int
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
Warning::
DNS resolution is slow (221 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 221 ms
A178.32.232.86
AAAA
CNAME
NSns4.esa.int, ns1.esa.int, ns2.esa.int, ns3.esa.int
MX
10 esa-int.mail.protection.outlook.com
TXT
mistral-domain-verification=d1485676252f23d98d837344d21e1295660fba87
atlassian-domain-verification=jc1Lc0lf5x4OG6wUf1JqVjrEnFMoFnZHGsM7vnwHu5E06MI333...
teamviewer-sso-verification=b2ff7cc25ea94cf49cf2db184ee9168e
MS=ms80437227
apple-domain-verification=qdRjdrwGfzXJfV9p
jmguggmgmek5a8u8t740g95og2
vmt1ojc581hlnck09q6sv40pup
pq46643sbh59a6p991v8sd3ime
2k4hqau0uurj3ubo4g9ebrqd2m
d365mktkey=3dsoa5x9hmg1homei7b782mz3
bt7fftvbt9racv7rgb9cnbccur
google-site-verification=LQgmlH1PAH3jhldXTrZL-l1fQGh8TCQxAB1okds6CLE
SPF v=spf1 a:spf.esa.int a:b.spf.service-now.com a:c.spf.service-now.com a:d.spf.ser...
jamf-site-verification=KKNcoh1pqhm8QO-IMN5-gw
cisco-ci-domain-verification=4193371e06eebcad78592e9db0ce795815e54d35c1bbbc3282d...
CAALookup not available with standard resolver
Resolved in 221 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.

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
Redirect Chain
1 redirect(s), 841 ms total
PASS
1 redirect(s), 841 ms total
Info::
Single redirect
Got: https://esa.int → https://www.esa.int/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 841 ms total
Got: 841 ms

https://esa.int

825 ms · HTTP/1.1

301

https://www.esa.int/

16 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://esa.int301825 msHTTP/1.1Apache
2https://www.esa.int/20016 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
esa.int — 30 years, 1 months old, hosted on OVH
PASS
esa.int — 30 years, 1 months old, hosted on OVH
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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: OVH
Got: AS16276
Domain expiry

Unknown

SSL certificate

197 days

Issued by Sectigo Limited

Domain age

30 years, 1 months

Registered August 23, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

178.32.232.86

Registrar

Registrar unknown

Unlocked 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created August 23, 1996 (30 years, 1 months ago)
Last Updated October 29, 2020
Name Servers ns1.esa.int, ns2.esa.int, ns3.esa.int, ns4.esa.int
DNSSEC Not enabled
Registrant European Space Agency (ESA)
Hosting
IP Address 178.32.232.86
ASN AS16276 (OVH, FR)
Provider OVH
Data source: rdap (1.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

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

Send Feedback