Skip to content
https://volaris.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
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 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.volaris.com/
200https://volaris.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://volaris.com/ http://www.volaris.com/

HTTP version does not redirect to HTTPS

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
189 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
A+
DNS Records
4 A records, 11 ms lookup
PASS
4 A records, 11 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.131.52, 151.101.3.52, 151.101.195.52, 151.101.67.52
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-133.awsdns-16.com, ns-1358.awsdns-41.org, ns-1613.awsdns-09.co.uk, ns-677.awsdns-20.net
Info::
2 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: 11 ms
Got: 11 ms
A151.101.131.52, 151.101.3.52, 151.101.195.52, 151.101.67.52
AAAA
CNAME
NSns-133.awsdns-16.com, ns-1358.awsdns-41.org, ns-1613.awsdns-09.co.uk, ns-677.awsdns-20.net
MX
10 mxb-00693e01.gslb.pphosted.com
10 mxa-00693e01.gslb.pphosted.com
TXT
include:_spf.psm.knowbe4.com ~all
358822c3cddc4375b2aaa08961519079
40LFKXK2VN5162POOGH3KBAYULOZGX7EXU0MBU1X
D8895313
MS=ms30673672
XTQS72GWDU9QJ1GFYNP8VPF6S5PUMA0YVGV1QBTF
atlassian-domain-verification=/dOu4DGVuibXj5Fy9LXRQ2Ov07Tjg4iaQBtAprk87VKmKBPfQt...
atlassian-sending-domain-verification=cce33b6d-d30d-405a-92c3-146b356742ec
google-gws-recovery-domain-verification=40897738
google-site-verification=1LfsowhFmaygpXvwyw7wLCodX8m3cQX-sukyEf9qv_o
google-site-verification=ATu5WMd805peZ5nbhSPNOVbM2j3L5wkjROzp7gGR-MU
google-site-verification=Oom5U- DcjpGkxm8LctYvUddSWwitV0lNih99Yu-rtUw
google-site-verification=TlmyWYe82tRuM_VV0WyCkbf6p9Up-3rCD1atuENs6-E
google-site-verification=eo_4xwkkDeDsWtl9okTnALQ0ZEkcz0emNzhkTEaEXJM
nup1l3k56bsak94k1igtles1gj
SPF v=spf1 ip4:52.201.86.119 ip4:100.24.214.111 ip4:192.161.146.64/28 ip4:198.11.248...
CAALookup not available with standard resolver
Resolved in 11 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
1 redirect(s), 36 ms total
PASS
1 redirect(s), 36 ms total
Info::
Single redirect
Got: https://volaris.com → https://www.volaris.com/ (301)
Info::
WWW normalization redirect

https://volaris.com

13 ms · HTTP/1.1

301

https://www.volaris.com/

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://volaris.com30113 msHTTP/1.1Varnish
2https://www.volaris.com/20023 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 278 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 278 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /Application/Error*
Disallow: /Application/InternalError*
Disallow: /Application/NotFound*
Disallow: /Member/ResetPassword*
Disallow: /Member/ForgotPassword*
Sitemap: https://www.volaris.com/sitemap.xml
Sitemap: https://www.volaris.com/sitemap_index.xml
sitemap.xml 200 OK
Type URL Set URLs 2 entries Valid XML Yes
A+
Domain Intelligence
volaris.com — via Amazon Registrar, Inc., 28 years, 6 months old, hosted on Fastly
PASS
volaris.com — via Amazon Registrar, Inc., 28 years, 6 months old, hosted on Fastly
Info::
Domain registered until Nov 2, 2033 (7 years, 7 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: Amazon Registrar, Inc.
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: Fastly
Got: AS54113
Domain expiry

2669 days

November 2, 2033

SSL certificate

189 days

Issued by Sectigo Limited

Domain age

28 years, 6 months

Registered February 18, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.131.52

Registrar

Amazon Registrar, Inc.

Unlocked 4 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Amazon Registrar, Inc.
Created February 18, 1998 (28 years, 6 months ago)
Expires November 2, 2033 (7 years, 7 months)
Last Updated November 2, 2023
Name Servers ns-133.awsdns-16.com, ns-1358.awsdns-41.org, ns-1613.awsdns-09.co.uk, ns-677.awsdns-20.net
DNSSEC Not enabled
Hosting
IP Address 151.101.131.52
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.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

A+
HTTP Probe Timing
Total 24 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 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.
17 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
24 ms
Total Time Total request time from DNS lookup through full response.
24 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 17 ms Server Processing 2 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-ewr-kewr1740047-EWR
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-ewr-kewr1740047-EWR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback