Skip to content
https://www.daraz.com.bd/#?

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
9
PASS
5
INFO
1
Probed from New York, United Stated
200 OK
Checks
17
5 PASS 9 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 193ms across 3 resolvers (spread 568ms)
FIX
Mean 193ms across 3 resolvers (spread 568ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Google: 570ms
Got: 570ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 568ms (min 2ms / max 570ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
F
HTTP Probe Timing
Action
Total 3753 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
542 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
310 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
703 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.02 s
Total Time Total request time from DNS lookup through full response.
3.75 s

Connection waterfall

DNS Lookup 542 ms TCP Connect 310 ms TLS Handshake 703 ms Server Processing 469 ms Content Transfer 1.73 s
C
DNS Records
Action
1 A records, 714 ms lookup
REVIEW
1 A records, 714 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 47.246.167.168
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: rg-sg.daraz.wagbridge.aserver-lazada.alibaba.com.gds.alibabadns.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (714 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 714 ms
A47.246.167.168
AAAA—
CNAMErg-sg.daraz.wagbridge.aserver-lazada.alibaba.com.gds.alibabadns.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 714 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

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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 47.246.167.168: lookup 47.246.167.168: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
197 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
C
CDN & Delivery
Action
Assets on Cloudflare (host img.lazcdn.com, 44 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host img.lazcdn.com, 44 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (img.lazcdn.com, 44 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation img.lazcdn.com.cdn.cloudflare.net
Info::
Assets on Cloudflare: img.lazcdn.com (assets: 44), cache HIT
Got: delegation img.lazcdn.com.cdn.cloudflare.net
Info::
Assets on Akamai: g.alicdn.com (assets: 5)
Got: delegation a1320.dscb.akamai.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • img.lazcdn.com — Cloudflare · assets: 44 · Cache Status: HIT
  • g.alicdn.com — Akamai · assets: 5

Other asset hosts

  • img.drz.lazcdn.com — assets: 66 · not attributed
  • g.lazcdn.com — assets: 33 · not attributed
  • sg.mmstat.com — assets: 7 · not attributed
  • ae01.alicdn.com — assets: 1 · below probe threshold
  • filebroker-cdn.lazada.sg — assets: 1 · below probe threshold
  • fourier.taobao.com — assets: 1 · below probe threshold
  • gw.alicdn.com — assets: 1 · below probe threshold
  • laz-img-cdn.alicdn.com — assets: 1 · below probe threshold
  • lzd-img-global.slatic.net — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.daraz.com.bd/#?

https://www.daraz.com.bd/#?

1753 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.daraz.com.bd/#?2001753 msHTTP/1.1Tengine/Aserver
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 241 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 241 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /checkout/
Disallow: /customer/
Disallow: /cart/
Disallow: /*index.scss
Disallow: /*reqwest/index
Disallow: /wangpu/
Disallow: /shop/*.htm
Disallow: /catalog/
Disallow: /*from=
Disallow: /wow/gcp/
Disallow: /wow/camp/
sitemap.xml 200 OK
Type Sitemap Index URLs 6 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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.daraz.com.bd/
301https://daraz.com.bd/

Preferred variant: www

HTTP → HTTPS

301http://www.daraz.com.bd/ → https://www.daraz.com.bd/

Consistent

A+
Health Check Endpoint
Health endpoint at https://www.daraz.com.bd/health (HTTP 200)
PASS
Health endpoint at https://www.daraz.com.bd/health (HTTP 200)
Info::
Public health endpoint at https://www.daraz.com.bd/health
Got: https://www.daraz.com.bd/health
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback