Skip to content
https://www.flipkart.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
4
PASS
4
INFO
0
Probed from Madrid, Spain
403 Forbidden
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.

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1226 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
42 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
197 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
196 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.23 s
Total Time Total request time from DNS lookup through full response.
1.23 s

Connection waterfall

DNS Lookup 42 ms TCP Connect 197 ms TLS Handshake 196 ms Server Processing 791 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
95 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

95
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, 58 ms lookup
PASS
1 A records, 58 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 163.53.76.86
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: flipkart.com
Info::
4 nameserver(s) configured
Got: sdns14.ultradns.com, sdns14.ultradns.org, sdns14.ultradns.biz, sdns14.ultradns.net
Info::
2 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: 58 ms
Got: 58 ms
A163.53.76.86
AAAA
CNAMEflipkart.com
NSsdns14.ultradns.com, sdns14.ultradns.org, sdns14.ultradns.biz, sdns14.ultradns.net
MX
1 eu-smtp-inbound-2.mimecast.com
1 eu-smtp-inbound-1.mimecast.com
TXT
_globalsign-domain-verification=l39_gF3zeh3avmm9ydAcg3ZXMojZJPlTAkkbG10oRj
google-site-verification=Y3dKKFu_H3cJ3l66OBt0QIUL3 Z6cXR0UxhulSdc28lY
clojars flipkartoss
adobe-idp-site-verification=a0fc98e1-5115-402f-8be0-49c4deadfd56
_globalsign-domain-verification=7UKZuWgB6vmpQnMirigM_Twxa1kE6tHsSwoTHqtv-K
_spf-emea.onbmc.com
google-site-verification=NEGJXq-YmreYBDEfw30NVnz5UAXk7nseky1T68T79fg
A2326006D53F012A497F
google-site-verification=a8AROMiT-DLHJdMYpl-bq-etV0NlpC5xDcKtHJDTVZ0
successfactors-site-verification=YTZlOTg4YzIwOWVlMWRmMGQ5ZGM0ODIzNDFhNjFlNDdlYzI...
n6266vWOmyPnlLRqgMEHQIWIafNmnJWQmWLR8MZZY6k=
onetrust-domain-verification=d61d9ce9635c4528b2a69148684e9a59
MS=ms55469658
MS=ms94028583
anthropic-domain-verification-r9whq9=BxHJo9teAvj2QK3PZPMKSbHPb
successfactors-site-verification=NjQzNDNlYjQ4NmUzZGE3ODMyMWIwZTNjNmEwZDIxMmNkNWQ...
google-site-verification=qe6w5aA7Jj6U8WPwr3p0bHFEIyn9xL5kBAb5iiaBUQA
MS=ms31449763
_globalsign-domain-verification=bUrRWaWTSLb6is-7YeKsgJGyITdBpbKwDuJFqHFmkw
_globalsign-domain-verification=Q80-agUf5T56LOyzndW3IUoJJU0dflC2v2q6duAIE1
H+GwmqnZHHJAKGepR+w0KFTUEH7YLcksjFI7avxc834=
_globalsign-domain-verification=1FkfdKwj6jnt7AK_UFbfIWv7kNCWaKRjFapuSUBHG8
tCrETfqtUKM7U/5AnUIFcFGnFbqfGExd8urSmdvq0cQ=
atlassian-domain-verification=WkV5HfBjxPmZapAUMERVsn8GyO5K6OMM5mDdGavD2buSbleKNw...
_globalsign-domain-verification=cWqZn5_MfmfRdWMn9D-zVG5s2UER1igw6oLMCu0ghW
SPF v=spf1 include:eu._netblocks.mimecast.com include:zoho.flipkart.com include:_spf...
atlassian-domain-verification=M7Fgf2m5Y3dL0wOH8QOisxTtYdGUlvoasctO8lKb1ordbAWmIm...
CAALookup not available with standard resolver
Resolved in 58 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.

A+
Redirect Chain
0 redirect(s), 491 ms total
PASS
0 redirect(s), 491 ms total

https://www.flipkart.com

491 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.flipkart.com403491 msHTTP/1.1
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.flipkart.com/
403https://flipkart.com/

HTTP → HTTPS

301http://www.flipkart.com/ https://www.flipkart.com:443/

Consistent

A
Domain Intelligence
flipkart.com — via GoDaddy.com, LLC, 19 years, 1 months old, hosted on FKNET-IN Flipkart Internet Pvt Ltd, IN
PASS
flipkart.com — via GoDaddy.com, LLC, 19 years, 1 months old, hosted on FKNET-IN Flipkart Internet Pvt Ltd, IN
Warning::
Domain expires in 52 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 3, 2026
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: GoDaddy.com, LLC
Info::
Hosting: FKNET-IN Flipkart Internet Pvt Ltd, IN
Got: AS9752
Domain expiry

EXPIRED

June 3, 2026

SSL certificate

95 days

Issued by GlobalSign nv-sa

Domain age

19 years, 1 months

Registered June 3, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

FKNET-IN Flipkart Internet Pvt Ltd, IN

ASN AS9752

163.53.76.86

Registrar

GoDaddy.com, LLC

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar GoDaddy.com, LLC
Created June 3, 2007 (19 years, 1 months ago)
Expires June 3, 2026 (1 months)
Last Updated June 4, 2025
Name Servers sdns14.ultradns.biz, sdns14.ultradns.com, sdns14.ultradns.net, sdns14.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 163.53.76.86
ASN AS9752 (FKNET-IN Flipkart Internet Pvt Ltd, IN)
Provider FKNET-IN Flipkart Internet Pvt Ltd, IN
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Send Feedback