Skip to content
https://uniqlo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
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 916 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
226 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
456 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
917 ms
Total Time Total request time from DNS lookup through full response.
917 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 226 ms TLS Handshake 456 ms Server Processing 229 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
220 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

220
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
A+
DNS Records
2 A records, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.194.27.64, 52.69.22.132
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1415.awsdns-48.org, ns-1728.awsdns-24.co.uk, ns-365.awsdns-45.com, ns-517.awsdns-00.net
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: 6 ms
Got: 6 ms
A52.194.27.64, 52.69.22.132
AAAA
CNAME
NSns-1415.awsdns-48.org, ns-1728.awsdns-24.co.uk, ns-365.awsdns-45.com, ns-517.awsdns-00.net
MX
0 uniqlo-com.mail.protection.outlook.com
10 mail1.uniqlo.co.jp
10 mail2.uniqlo.co.jp
30 mail3.uniqlo.co.jp
30 mail4.uniqlo.co.jp
TXT
MS=ms41076334
docker-verification=60564edc-d337-4e9e-991d-07436b9d977e
globalsign-domain-verification=8frsHcE2ag-0ccaaP5BTpPmUJC8ob8pdjDQchfAWzD
google-site-verification=0UT-z64W0J5yIPZjVp9z89xxtdOKGkYsjh_6_xlkUXk
google-site-verification=TOzPitzvAELGdmY0u_D71L_dI_SxNPUKOlRSVtEBLX4
google-site-verification=bckecCEpwoT9SLSISmWzymbRrvxeFTe_3s0s_AQL8yU
google-site-verification=cbtrAUPiy4nLPZTr73VXOVSfQB7AAfga69PqJxNQBnQ
klaviyo-site-verification=RfdYdh
pardot1103682=6b9f2dd532ecb3c8ca1dc0fd11a47d3f8f555e7bc275560047fe18999d24b59a
sending_domain1103682=1ad338e36509f394e79d0125266095d5b5aed6b0fba06c872433a27106...
u32VomAlnR94FNu4DroBREX04HYoA7AVC5rcr47dCTKxel27q57N+z/KpRQ9bciRiLp3RZvSzGC3Zgit...
SPF v=spf1 include:spf.servicemail24.de include:spf.protection.outlook.com +ip4:211....
CAALookup not available with standard resolver
Resolved in 6 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+
Redirect Chain
0 redirect(s), 915 ms total
PASS
0 redirect(s), 915 ms total
Info::
Redirect overhead: 915 ms total
Got: 915 ms

https://uniqlo.com

915 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uniqlo.com301915 msHTTP/1.1nginx
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

https://www.uniqlo.com/
200https://uniqlo.com/

HTTP → HTTPS

301http://uniqlo.com/ https://uniqlo.com:443/

Consistent

A+
Domain Intelligence
uniqlo.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on AWS
PASS
uniqlo.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on AWS
Info::
Domain registered until Dec 28, 2026 (8 months remaining)
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: MarkMonitor 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: AWS
Got: AS16509
Domain expiry

197 days

December 28, 2026

SSL certificate

220 days

Issued by Amazon

Domain age

27 years, 8 months

Registered December 28, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.194.27.64

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created December 28, 1998 (27 years, 8 months ago)
Expires December 28, 2026 (8 months)
Last Updated September 2, 2025
Name Servers ns-1415.awsdns-48.org, ns-1728.awsdns-24.co.uk, ns-365.awsdns-45.com, ns-517.awsdns-00.net
DNSSEC Not enabled
Hosting
IP Address 52.194.27.64
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.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

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

Send Feedback