Skip to content
https://oanda.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 637 ms total
FIX
3 redirect(s), 637 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.oanda.com/
Info::
Redirect overhead: 637 ms total
Got: 637 ms

https://oanda.com

59 ms · HTTP/1.1

301

https://www.oanda.com/

296 ms · HTTP/1.1

302

https://www.oanda.com/eu-en/

116 ms · HTTP/1.1

301

https://www.oanda.com/eu-en

166 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://oanda.com30159 msHTTP/1.1cloudflare
2https://www.oanda.com/302296 msHTTP/1.1cloudflare
3https://www.oanda.com/eu-en/301116 msHTTP/1.1cloudflare
4https://www.oanda.com/eu-en200166 msHTTP/1.1cloudflare

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

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

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

Certificate validity

48
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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f00adb46ecad30d-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f00adb46ecad30d-CDG
A+
DNS Records
2 A records, 93 ms lookup
PASS
2 A records, 93 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.37.191, 104.17.38.191
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: henrik.ns.cloudflare.com, may.ns.cloudflare.com
Info::
5 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: 93 ms
Got: 93 ms
A104.17.37.191, 104.17.38.191
AAAA—
CNAME—
NShenrik.ns.cloudflare.com, may.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
google-site-verification=2fJ3rN-sHvPOKfH8LSjEJpF9lwK-kInVVyWJX4pMqBE
cursor-domain-verification-gpdby0=rGZ1GvKUyvTxMOc78zJpsNycc
google-site-verification=ol87472m802HOH6TBovJeJJAtlzzR8iN5g8m1UxceZs
docker-verification=21b634d3-755a-4cac-8337-2d276b5f896e
adobe-idp-site-verification=a5c399b9463ad85a558de6e93c27ba4808648ac3becbde6e7fb8...
MS=C98ED1ACBD008154491FEEAB6D3272112C9F35D6
SPF v=spf1 ip4:198.105.26.0/23 ip4:192.247.0.0/24 ip4:167.89.63.175 ip4:208.117.48.1...
apple-domain-verification=mWYbPflDFnm5Jryu
h1-domain-verification=vjkjQPFn2gUEEnbFxoctDZkHFCJZAWT8XBcR39bxFwanPUkA
duo_sso_verification=D3RCsGnHtdieusRnsB3NNF6RaX6gkDWvvs66s20EJEUdZ8F4ipNkGl9qn6Z...
segment-site-verification=vKa5G4XNOwesmwqNbv7jbeqOYlERAGCt
facebook-domain-verification=r1q0ucz5d7pc49c2kq3jpdh5gd3kn9
nitro-verification-code=LTE5NTY5OTYyNzMwNDk0MTgwNDg=
CAALookup not available with standard resolver
Resolved in 93 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+
Crawlability
robots.txt present, sitemap with 23 URLs
PASS
robots.txt present, sitemap with 23 URLs
Info::
robots.txt is present
Got: 378 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 378 B Sitemaps referenced 1 User-agents *, VelenPublicWebCrawler Blocking No — crawling allowed
User-agent: *

Disallow: /account/password-reset/

Disallow: /demo-account/password-reset/

Disallow: /*/account/password-reset/

Disallow: /*/demo-account/password-reset/

Disallow: /site/terms-of-use

Disallow: /site/disclaimer

Disallow: /resources/thank_you

Disallow: *?*


User-agent: VelenPublicWebCrawler

Disallow: /


Sitemap: https://www.oanda.com/sitemap_index.xml
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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://oanda.com/ → https://oanda.com/

Consistent

A+
Domain Intelligence
oanda.com — via Tucows Domains Inc., 30 years, 1 months old, hosted on Cloudflare
PASS
oanda.com — via Tucows Domains Inc., 30 years, 1 months old, hosted on Cloudflare
Info::
Domain registered until Aug 3, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Tucows Domains 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: Cloudflare
Got: AS13335
Domain expiry

16 days

August 3, 2026

SSL certificate

48 days

Issued by Google Trust Services

Domain age

30 years, 1 months

Registered August 4, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.37.191

Registrar

Tucows Domains Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created August 4, 1996 (30 years, 1 months ago)
Expires August 3, 2026 (3 months)
Last Updated July 5, 2025
Name Servers henrik.ns.cloudflare.com, may.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.17.37.191
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

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 87 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
88 ms
Total Time Total request time from DNS lookup through full response.
88 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 18 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