Skip to content
https://www.emirates.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
4
PASS
4
INFO
0
Probed from Santa Clara, United Stated
307 Temporary Redirect
Checks
9
4 PASS 4 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.

B
DNS Records
1 A records, 11 ms lookup
REVIEW
1 A records, 11 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.40.24.105
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: e2772.x.akamaiedge.net
Info::
No NS records found
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: 11 ms
Got: 11 ms
A23.40.24.105
AAAA—
CNAMEe2772.x.akamaiedge.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 11 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

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)

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.emirates.com/
301https://emirates.com/

Preferred variant: www

HTTP → HTTPS

302http://www.emirates.com/ → http://www.emirates.com/error/accessrestricted.html?refid=18.4a7cb17.1775594549.3ee70efe

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Redirect Chain
1 redirect(s), 358 ms total
PASS
1 redirect(s), 358 ms total
Info::
Single redirect
Got: https://www.emirates.com → https://www.emirates.com/us/english/ (307)

https://www.emirates.com

50 ms · HTTP/1.1

307

https://www.emirates.com/us/english/

308 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.emirates.com30750 msHTTP/1.1
2https://www.emirates.com/us/english/200308 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

Disallow: /SessionHandler.aspx

Disallow: /TealeafTarget.aspx

Disallow: /sessionhandler.aspx

Disallow: /tealeaftarget.aspx

Disallow: /sessionkeepalive.aspx

Disallow: /*/ExternalTransfer.aspx?

Disallow: /*?Cookie=true

Disallow: /*?*intcid=*

Disallow: /WebResource.axd

Disallow: /resources

Disallow: /*/pop-ups/

Disallow: /*/system/click/tracking.aspx

Disallow: /*/mail-to-friend.aspx

Disallow: /*/mailtofriend.aspx

Disallow: /*/certificate-request/*/certificate-request/*

Disallow: /*/destinations/city.aspx*

Disallow: /*/destinations/airport.aspx*

Disallow: /*/experience/login/

Disallow: /*/ekgroup/id*

Disallow: /*flightstatus-results.aspx?

Disallow: /*/woyf/?*h=

Disallow: /*/find-visa-requirements.aspx?

Disallow: /*/find-visa-requirements-results.aspx?

Disallow: /*/featured-fares/?*airport*

Disallow: /*/sso/login-redirect

Disallow: /*/service/dex/request-handler

Disallow: /*/service/dex/request-handler-page

Disallow: /booking/*


Host: www.emirates.com
Sitemap: https://www.emirates.com/sitemapindex.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 170 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
emirates.com — via MarkMonitor Inc., 30 years, 1 months old, hosted on Akamai
PASS
emirates.com — via MarkMonitor Inc., 30 years, 1 months old, hosted on Akamai
Info::
Domain registered until Jul 24, 2027 (1 years, 3 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: MarkMonitor Inc.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

422 days

July 24, 2027

SSL certificate

199 days

Issued by DigiCert Inc

Domain age

30 years, 1 months

Registered July 25, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.40.24.105

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created July 25, 1996 (30 years, 1 months ago)
Expires July 24, 2027 (1 years, 3 months)
Last Updated June 22, 2025
Name Servers a1-127.akam.net, a11-64.akam.net, a2-65.akam.net, a24-66.akam.net, a6-67.akam.net, a7-64.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.40.24.105
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.2s)

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 36 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.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
36 ms
Total Time Total request time from DNS lookup through full response.
37 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 23 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