Skip to content
https://vueling.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1100 ms total
FIX
2 redirect(s), 1100 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1100 ms total
Got: 1100 ms

https://vueling.com

445 ms · HTTP/1.1

301

https://www.vueling.com/

461 ms · HTTP/1.1

301

https://www.vueling.com/en

194 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vueling.com301445 msHTTP/1.1AkamaiGHost
2https://www.vueling.com/301461 msHTTP/1.1AkamaiGHost
3https://www.vueling.com/en200194 msHTTP/1.1Kestrel

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
Domain Intelligence
vueling.com — via EuroDNS S.A., 23 years, 3 months old, hosted on Akamai
REVIEW
vueling.com — via EuroDNS S.A., 23 years, 3 months old, hosted on Akamai
Critical::
Domain expires in 23 days
This domain expires on May 9, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 9, 2026
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.
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: Akamai
Got: AS16625
Domain expiry

EXPIRED

May 9, 2026

SSL certificate

121 days

Issued by DigiCert Inc

Domain age

23 years, 3 months

Registered May 9, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

104.123.100.47

Registrar

EuroDNS S.A.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar EuroDNS S.A.
Created May 9, 2003 (23 years, 3 months ago)
Expires May 9, 2026 (23 days)
Last Updated May 3, 2025
Name Servers a1-17.akam.net, a13-64.akam.net, a2-65.akam.net, a4-66.akam.net, a7-67.akam.net, a8-64.akam.net
DNSSEC Not enabled
Hosting
IP Address 104.123.100.47
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.1s)

This domain expires on May 9, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

121
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 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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 23 ms lookup
PASS
1 A records, 23 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.123.100.47
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a2-65.akam.net, a13-64.akam.net, a7-67.akam.net, a8-64.akam.net, a4-66.akam.net, a1-17.akam.net
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
Info::
DNS resolution time: 23 ms
Got: 23 ms
A104.123.100.47
AAAA—
CNAME—
NSa2-65.akam.net, a13-64.akam.net, a7-67.akam.net, a8-64.akam.net, a4-66.akam.net, a1-17.akam.net
MX
10 vueling-com.mail.protection.outlook.com
TXT
docusign=badacfb0-06b8-4b4e-913f-c9ef33c6f5fd
MS=ms54932483
MS=ms68403550
docusign=52c5d98f-b2bc-458f-b1be-adc7b280a1e4
J3JnHptzNTdC8r8oUHJA9z5FTeVG/0ClDeHATQCm5cPfg0PST3UKbrIN5qIoLI7TJsmaVwrIJUtnjM4v...
google-site-verification=NRF0a0mnl_zSzhJfMBKaWTAu2cTIN9vXDvWt2nxLARo
work-accounts-domain-verification=rHhAVRRXrlBnk9Sk7VLh3wcjKmo9uV
openai-domain-verification=dv-is7TpQGUgpHSCGAmqpvlTbM1
google-site-verification=Ci2S10OEBnuk4S1sedOl3FA6s5n2BZ5ltK7-uomKE3c
vmware-cloud-verification-6f53689f-c6dc-49b1-8a46-e07aae5ef30a
SPF v=spf1 include:nexica.com include:spf.vueling.com ip4:83.169.91.111 ip4:83.169.9...
autodesk-domain-verification=ZzvrwlMlM-3HSjU1TrCE
onetrust-domain-verification=ad3057d497b24064af2d3baf73b97b36
apple-domain-verification=32FR5oaGe3L8aVKd
3hLJ_wOuwuEsFeTEPXJX
v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/nQiSF4Ga2ZTsk2dl1...
facebook-domain-verification = p8u7rjhn9mhlyp1s4o8brx1chzygbo
atlassian-domain-verification=dfxH1/CKP8kFJ0uYKTxlCKo6hJPiDY6ahF1OkBnsJabRqbJPE4...
CAALookup not available with standard resolver
Resolved in 23 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+
Crawlability
robots.txt present, sitemap with 23 URLs
PASS
robots.txt present, sitemap with 23 URLs
Info::
robots.txt is present
Got: 674 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 23 entries
Info::
Sitemap index with 23 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 674 B Sitemaps referenced 2 User-agents AhrefsBot, msnbot, * Blocking No — crawling allowed
Sitemap: https://www.vueling.com/mapsite


Sitemap: https://www.vueling.com/faq/faq-sitemap.xml


User-agent: *


Allow: /


Disallow: /*?mode=


Disallow: /*?sid=


Disallow: /*?language=


Disallow: /*?keyword=


Disallow: /*?nomob=


Disallow: /*?id=


Disallow: /*?cadw=


Disallow: /*?city=


Disallow: /*?idioma=


Disallow: /*?ip=


Disallow: /*?originCalendar=


Disallow: /*?destinationCalendar=


Disallow: /flights-stockholm/


Disallow: /tarifas-vueling/


 

Disallow: /skylights/


Disallow: /cities/


Disallow: /info/


Disallow: /investors/


 

user-agent: AhrefsBot


disallow: /


 

User-agent: msnbot


Crawl-delay: 300
sitemap.xml 200 OK
Type Sitemap Index URLs 23 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.vueling.com/
200https://vueling.com/

HTTP → HTTPS

301http://vueling.com/ → https://www.vueling.com/

Consistent

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

Connection waterfall

DNS Lookup 7 ms TCP Connect 144 ms TLS Handshake 148 ms Server Processing 161 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