Infrastructure - https://dji.com BeaverCheck Audit

B

Redirect Chain

2 redirect(s), 506 ms total

REVIEW

2 redirect(s), 506 ms total

2 redirects before reaching final URL

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

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.dji.com/

Redirect overhead: 506 ms total

Got: 506 ms

https://dji.com

22 ms · HTTP/1.1

301

https://www.dji.com/

342 ms · HTTP/1.1

302

https://www.dji.com/sg

142 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://dji.com	301	22 ms	HTTP/1.1	CloudFront
2	https://www.dji.com/	302	342 ms	HTTP/1.1	openresty
3	https://www.dji.com/sg	200	142 ms	HTTP/1.1	openresty

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

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

185 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

185

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 (LambdaGeneratedResponse from cloudfront)

REVIEW

AWS CloudFront (LambdaGeneratedResponse from cloudfront)

Site is served via AWS CloudFront CDN (edge: SIN2-P7)

Got: x-amz-cf-id: EUPVsEQgnDghH5tKfS9mAcnROzkuWCO3SyVOZWGr6U_7R8qBszlW2A==

CDN cache status: LambdaGeneratedResponse from cloudfront

CDN Detected: AWS CloudFront

Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: EUPVsEQgnDghH5tKfS9mAcnROzkuWCO3SyVOZWGr6U_7R8qBszlW2A==

A+

DNS Records

4 A records, 100 ms lookup

PASS

4 A records, 100 ms lookup

Resolves to 4 IPv4 address(es)

Got: 13.35.202.15, 13.35.202.29, 13.35.202.47, 13.35.202.119

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1313.awsdns-36.org, ns-1991.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-647.awsdns-16.net

3 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 100 ms

Got: 100 ms

A	13.35.202.15, 13.35.202.29, 13.35.202.47, 13.35.202.119
AAAA	—
CNAME	—
NS	ns-1313.awsdns-36.org, ns-1991.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-647.awsdns-16.net
MX	5 mail.djicorp.com 10 mail2.djicorp.com 10 mail3.djicorp.com
TXT	MS=ms14241538 aliyun-site-verification=1ddefcd9-dded-4c33-84a6-180d69b1cdb6 facebook-domain-verification=ml92pp9umnegytjzme8snzfqg6wzl8 facebook-domain-verification=op1wlt3teryi12abilw4wibrbvz657 google-site-verification=Qd2bvYVdjze_5iXL46UPzctfaeME5k0gCf6LqKZ2VpU google-site-verification=SIYax7LUNHsOslT8hzzV1fmNJ-j2Iu6kTYk_MAKjIN0 google-site-verification=eU3dIczNAfIdxZejHGGP_Jba6eCX1cS2GoceDBIOaJ0 google-site-verification=fhO47r7f6yeHmzBNFeBuRkVgDycQUjrttzf5b1tHSsI google-site-verification=leX04oqxj0mRvWHqvdTvOxoICUQ0BQ9kT1uzvAf7wQs google-site-verification=nTxXb9ujsYi5I6ielIoQE5fm_G9mD3oa9_7vx889m5o shopify-verification-code=HTT004LLViCyyyOA18GovAPKAPm3PH SPF v=spf1 include:spf.dji.com include:mailgun.org include:mail.zendesk.com include:... zoho-verification=zb57545151.zmverify.zoho.com.cn zoho-verification=zb59681615.zmverify.zoho.com
CAA	Lookup not available with standard resolver

Resolved in 100 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 37 URLs

PASS

robots.txt present, sitemap with 37 URLs

robots.txt is present

Got: 926 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 37 entries

Sitemap index with 37 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 926 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /cache/
Disallow: /wp-admin/
Disallow: /wp-includes
Disallow: /wp-content/themes/
Disallow: /newsletter/
Disallow: /register
Disallow: /page/
Disallow: /*/page/
Disallow: /order/
Disallow: /*/order/
Disallow: /orders/
Disallow: /*/orders/
Disallow: /user/
Disallow: /*/user/
Disallow: /*/change-lang*
Disallow: /change-lang*
Disallow: /*/dealer
Disallow: /*?www=v1
Disallow: /*?page
Disallow: /*?__
Disallow: /*preview
Disallow: /*?hc_
Disallow: /*?clickaid
Disallow: /*?viewType
Disallow: /*?gclid
Disallow: /*?utm
Disallow: /*?guid
Disallow: /*?r
Disallow: /*?iframe
Disallow: /*/change-country*
Disallow: /change-country*
Disallow: /*cache
Disallow: /search*
Disallow: /*/search*
Disallow: /*&www=v1
Disallow: /*/company
Disallow: /*/contact
Disallow: /*/policy
Disallow: /*/terms
Disallow: /*/feedback
Disallow: /*/sitemap
Disallow: /*/mobile/mimo/activity
Sitemap: https://www.dji.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 37 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.dji.com/

200https://dji.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

dji.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 30 years, 8 months old, hosted on AWS

PASS

dji.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 30 years, 8 months old, hosted on AWS

Domain registered until Mar 1, 2030 (3 years, 10 months remaining)

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.

Registrar: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)

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.

Hosting: AWS

Got: AS16509

Domain expiry

1322 days

March 1, 2030

SSL certificate

185 days

Issued by Amazon

Domain age

30 years, 8 months

Registered January 16, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.35.202.29

Registrar

Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)

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 Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)

Created January 16, 1996 (30 years, 8 months ago)

Expires March 1, 2030 (3 years, 10 months)

Last Updated April 26, 2024

Name Servers ns-1313.awsdns-36.org, ns-1991.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-647.awsdns-16.net

DNSSEC Not enabled

Hosting

IP Address 13.35.202.29

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (1.3s)

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 20 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

2 ms

TCP Connect

1 ms

TLS Handshake

3 ms

Time to First Byte

20 ms

Total Time

20 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 14 ms Content Transfer 0 ms