Skip to content
https://www.ryanair.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
225 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

225
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: AMS58-P2)
Got: x-amz-cf-id: q18uN4nlwoIfDTQagGg7TW6-Bl8-VSHg95eX6pI2ygOrGMB6oVF1RA==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: q18uN4nlwoIfDTQagGg7TW6-Bl8-VSHg95eX6pI2ygOrGMB6oVF1RA==
A
DNS Records
4 A records, 14 ms lookup
PASS
4 A records, 14 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.239.36.4, 18.239.36.46, 18.239.36.110, 18.239.36.20
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:20a0:3600:11:ba7:69c0:93a1, 2600:9000:20a0:7400:11:ba7:69c0:93a1, 2600:9000:20a0:5000:11:ba7:69c0:93a1, 2600:9000:20a0:8e00:11:ba7:69c0:93a1, 2600:9000:20a0:5a00:11:ba7:69c0:93a1, 2600:9000:20a0:c800:11:ba7:69c0:93a1, 2600:9000:20a0:e600:11:ba7:69c0:93a1, 2600:9000:20a0:e200:11:ba7:69c0:93a1
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d37en9p9pf4plz.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1087.awsdns-07.org, ns-1936.awsdns-50.co.uk, ns-469.awsdns-58.com, ns-933.awsdns-52.net
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 14 ms
Got: 14 ms
A18.239.36.4, 18.239.36.46, 18.239.36.110, 18.239.36.20
AAAA2600:9000:20a0:3600:11:ba7:69c0:93a1, 2600:9000:20a0:7400:11:ba7:69c0:93a1, 2600:9000:20a0:5000:11:ba7:69c0:93a1, 2600:9000:20a0:8e00:11:ba7:69c0:93a1, 2600:9000:20a0:5a00:11:ba7:69c0:93a1, 2600:9000:20a0:c800:11:ba7:69c0:93a1, 2600:9000:20a0:e600:11:ba7:69c0:93a1, 2600:9000:20a0:e200:11:ba7:69c0:93a1
CNAMEd37en9p9pf4plz.cloudfront.net
NSns-1087.awsdns-07.org, ns-1936.awsdns-50.co.uk, ns-469.awsdns-58.com, ns-933.awsdns-52.net
MX
TXT
CAALookup not available with standard resolver
Resolved in 14 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 313 ms total
PASS
1 redirect(s), 313 ms total
Info::
Single redirect
Got: https://www.ryanair.com → https://www.ryanair.com/nl/nl (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.ryanair.com

https://www.ryanair.com

266 ms · HTTP/1.1

302

https://www.ryanair.com/nl/nl

47 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.ryanair.com302266 msHTTP/1.1CloudFront
2https://www.ryanair.com/nl/nl20047 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:9000:20a0:3600:11:ba7:69c0:93a1, 2600:9000:20a0:7400:11:ba7:69c0:93a1, 2600:9000:20a0:5000:11:ba7:69c0:93a1, 2600:9000:20a0:8e00:11:ba7:69c0:93a1, 2600:9000:20a0:5a00:11:ba7:69c0:93a1, 2600:9000:20a0:c800:11:ba7:69c0:93a1, 2600:9000:20a0:e600:11:ba7:69c0:93a1, 2600:9000:20a0:e200:11:ba7:69c0:93a1
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:9000:20a0:3600:11:ba7:69c0:93a1, 2600:9000:20a0:7400:11:ba7:69c0:93a1, 2600:9000:20a0:5000:11:ba7:69c0:93a1, 2600:9000:20a0:8e00:11:ba7:69c0:93a1, 2600:9000:20a0:5a00:11:ba7:69c0:93a1, 2600:9000:20a0:c800:11:ba7:69c0:93a1, 2600:9000:20a0:e600:11:ba7:69c0:93a1, 2600:9000:20a0:e200:11:ba7:69c0:93a1 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 236 URLs
PASS
robots.txt present, sitemap with 236 URLs
Info::
robots.txt is present
Got: 718 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 236 entries
Info::
Sitemap index with 236 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 718 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
user-agent: *
allow: /
 
disallow: /*/*/deactive-account
disallow: /*/*/emailChangeConfirm
disallow: /*/*/forgotpassword
disallow: /*/*/reset-password
disallow: /*/*/resetsuccess
disallow: /*/*/reset
disallow: /*/*/lock-account
disallow: /*/*/unlock
disallow: /*/*/verifyemail
disallow: /*/*/reactivate
disallow: /*/*/reactivate-account-succeed
disallow: /*/*/booking
disallow: /*/*/mytrips
disallow: /*/*/paypal
disallow: /*/*/samsonite/
disallow: /*/*/vouchers/
disallow: /*/*/?cmpid=
disallow: /*/*/foh.
disallow: /*/*/rooms/
disallow:/*?promo-code=ABCDE
disallow: /*/*/trip
disallow: /*/*/search/flights
disallow: /redirect
disallow: /*/*/boarding-pass
disallow: /api

sitemap: https://www.ryanair.com/sitemap.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 236 entries Valid XML Yes
Child Sitemaps:
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ryanair.com/
302https://ryanair.com/

Preferred variant: www

HTTP → HTTPS

301http://www.ryanair.com/ https://www.ryanair.com/

Consistent

A+
Domain Intelligence
ryanair.com — via EuroDNS S.A., 30 years, 2 months old
PASS
ryanair.com — via EuroDNS S.A., 30 years, 2 months old
Info::
Domain registered until Jul 11, 2031 (5 years, 4 months remaining)
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.
Info::
Registrar: EuroDNS S.A.
Domain expiry

1825 days

July 11, 2031

SSL certificate

225 days

Issued by DigiCert Inc

Domain age

30 years, 2 months

Registered July 12, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:218f:1400:13:9354:3800:93a1

Registrar

EuroDNS S.A.

Lock status unknown 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar EuroDNS S.A.
Created July 12, 1996 (30 years, 2 months ago)
Expires July 11, 2031 (5 years, 4 months)
Last Updated March 27, 2025
Name Servers edns6.ultradns.biz, edns6.ultradns.com, edns6.ultradns.net, edns6.ultradns.org, ns99.ultradns2.com, ns99.ultradns2.org
DNSSEC Not enabled
Hosting
IP Address 2600:9000:218f:1400:13:9354:3800:93a1
Data source: rdap (0.0s)

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

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

Connection waterfall

DNS Lookup 50 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 4 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