Skip to content
https://patagonia.co.kr

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
10
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
17
5 PASS 10 REVIEW 2 FIX
F
Crawlability
Action
robots.txt present, sitemap with 0 URLs
FIX
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 206 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 206 B Sitemaps referenced 0 User-agents Twitterbot, Yeti, Daumoa, *, Googlebot, cowbot, NaverBot Blocking Yes — all crawlers blocked
User-agent: Googlebot
Allow: /

User-agent: cowbot
Allow: /

User-agent: NaverBot
Allow: /

User-agent: Twitterbot
Allow: *

User-agent: Yeti
Allow: /

User-agent: Daumoa
Allow: /

User-agent: *
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.

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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 101.79.14.73: lookup 101.79.14.73: 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.
Info::
PTR lookup failed for 110.165.23.204: lookup 110.165.23.204: 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
Multi-Resolver DNS Speed
Action
Mean 104ms across 3 resolvers (spread 281ms)
REVIEW
Mean 104ms across 3 resolvers (spread 281ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 25ms
Got: 25ms via 9.9.9.9:53
Info::
Google: 285ms
Got: 285ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 281ms (min 4ms / max 285ms)
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.
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.patagonia.co.kr/
200https://patagonia.co.kr/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://patagonia.co.kr/ → https://patagonia.co.kr:443/

Consistent

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 254 ms TLS Handshake 260 ms Server Processing 510 ms Content Transfer 67 ms
C
TLS Certificate Expiry & Recommendations
Action
20 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

20
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 20 days remaining
  • 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 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+
DNS Records
2 A records, 48 ms lookup
PASS
2 A records, 48 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 101.79.14.73, 110.165.23.204
Info::
No IPv6 (AAAA) records
Info::
7 nameserver(s) configured
Got: ns5.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns1.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 48 ms
Got: 48 ms
A101.79.14.73, 110.165.23.204
AAAA—
CNAME—
NSns5.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns1.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com
MX
10 patagonia-co-kr.mail.protection.outlook.com
TXT
MS=ms36840604
SPF v=spf1 include:spf.protection.outlook.com include:email.ncloud.com ip4:222.239.1...
google-site-verification=cmtpl9XdYMsHaUrVEhHeL0HBpG1dJYjqc-XpYFQXNVM
mailer.domain.verification=1cAhcSmkWDo0ugKqzuvwirUaZUdB3J
CAALookup not available with standard resolver
Resolved in 48 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://patagonia.co.kr

https://patagonia.co.kr

1027 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://patagonia.co.kr2001027 msHTTP/1.1Apache/2.4.67 (Red Hat Enterprise Linux) OpenSSL/3.0.20 PHP/7.4.33
A+
Domain Intelligence
patagonia.co.kr — via Whois Corp.(http://whois.co.kr), hosted on NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG
PASS
patagonia.co.kr — via Whois Corp.(http://whois.co.kr), hosted on NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG
Info::
Registrar: Whois Corp.(http://whois.co.kr)
Info::
Hosting: NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG
Got: AS135354
Domain expiry

Unknown

SSL certificate

20 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG

ASN AS135354

101.79.14.73

Registrar

Whois Corp.(http://whois.co.kr)

Lock status unknown 7 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
Registrar Whois Corp.(http://whois.co.kr)
Name Servers ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com
Hosting
IP Address 101.79.14.73
ASN AS135354 (NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG)
Provider NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD., SG
Data source: whois (2.3s)
A+
Health Check Endpoint
Health endpoint at https://patagonia.co.kr/health (HTTP 200)
PASS
Health endpoint at https://patagonia.co.kr/health (HTTP 200)
Info::
Public health endpoint at https://patagonia.co.kr/health
Got: https://patagonia.co.kr/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback