Infrastructure - https://oppo.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 1249 ms total

FIX

2 redirect(s), 1249 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.oppo.com/

Redirect overhead: 1249 ms total

Got: 1249 ms

https://oppo.com

829 ms · HTTP/1.1

301

https://www.oppo.com/

31 ms · HTTP/1.1

302

https://www.oppo.com/en/

390 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://oppo.com	301	829 ms	HTTP/1.1	nginx
2	https://www.oppo.com/	302	31 ms	HTTP/1.1	AkamaiGHost
3	https://www.oppo.com/en/	200	390 ms	HTTP/1.1	nginx

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

D

CDN & Delivery

Action

No CDN detected

FIX

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.

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

93 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

93

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

A+

DNS Records

1 A records, 80 ms lookup

PASS

1 A records, 80 ms lookup

Resolves to 1 IPv4 address(es)

Got: 106.3.18.178

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns4.dnsv5.com, ns3.dnsv5.com

1 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: 80 ms

Got: 80 ms

A	106.3.18.178
AAAA	—
CNAME	—
NS	ns4.dnsv5.com, ns3.dnsv5.com
MX	5 oppo-com.mail.protection.outlook.com
TXT	6p2cjcng7bf5jk2wbndw17dg3232dwpf 6w4jv2qk2mchhpwg9b3pc3j3knwwslm0 _9msb5bc9llar37gnce30r00aricrch9 _gbcq6dyt21b0qcgykbyuvow19cnqzht _xk5uo1q9jt3jjn4ynlay797g4hcw3k9 j25g3xq2n0yq0p3mnyfs2j95t8qqp19p scv81k25v7nxt3dstns8j5q2lznlm4kn ZOOM_verify_xnRWrrRUS2CvI07geRYOyg cursor-domain-verification-9h75aw=yhlIk5DHInIIuzWQsSUrjiC2A 31961b884b470a8aca7bcf041e9079269761db4744fb5b0e2594a0c1b9593a2b SPF v=spf1 include:spf.protection.outlook.com include:spf.oppo.com -all google-site-verification=M_uo3myAF1E28gPQvnsl2i-VMFIxu5Ptb2JNiiCslp4 google-site-verification=Qz8qTPuhHsGqV9KayX6qKNEEDSCUweL7yE08ro5yUPA google-site-verification=W6bKERKBqBTuZ8HYJKcVfFnUaT6hp6KbR0xjPvg5U5Y qqmail-site-verification=fcaf0e4d805162fa17b785ec5fb93fcf024c79b6ff7 BIdqtdjceeYiZ2/g0weVLtNCHsB579ypC1zwTXLNwqtzvMVSMFfu2db7KOlAB540lA6Xz1h1wkAgM2hO... figma-domain-verification=f174d908d81f1f46f7e1b0985d4553d26447390e6846253e74232e... 0bp26lbw50n9jx4hjjkhlf3x1myvbs7l 2bz9n3gbtrjx5zhy5mbv9qrw17j6t497
CAA	Lookup not available with standard resolver

Resolved in 80 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 92 URLs

PASS

robots.txt present, sitemap with 92 URLs

robots.txt is present

Got: 56 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 92 entries

Sitemap index with 92 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *

Sitemap: https://www.oppo.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 92 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.oppo.com/

200https://oppo.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

oppo.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 27 years, 8 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

PASS

oppo.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 27 years, 8 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

Domain registered until Dec 16, 2029 (3 years, 8 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 (Beijing) Co., Ltd.

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: CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

Got: AS23724

Domain expiry

1249 days

December 16, 2029

SSL certificate

93 days

Issued by DigiCert, Inc.

Domain age

27 years, 8 months

Registered December 16, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

ASN AS23724

106.3.18.178

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 2 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 (Beijing) Co., Ltd.

Created December 16, 1998 (27 years, 8 months ago)

Expires December 16, 2029 (3 years, 8 months)

Last Updated January 2, 2024

Name Servers ns3.dnsv5.com, ns4.dnsv5.com

DNSSEC Not enabled

Hosting

IP Address 106.3.18.178

ASN AS23724 (CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN)

Provider CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

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

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

PASS

DNS Lookup

11 ms

TCP Connect

218 ms

TLS Handshake

221 ms

Time to First Byte

668 ms

Total Time

668 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 218 ms TLS Handshake 221 ms Server Processing 218 ms Content Transfer 0 ms