Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records1 A records, 35 ms lookupREVIEW
| A | 23.222.61.145 |
| AAAA | — |
| CNAME | www.patagonia.com_dw_pm-v2.edgekey.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
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)
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!-- saved from url=(0055)file:///Users/jreyesco/Downloads/botfailover%20(5).html -->
<html class="no-js" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><style type="text/css"></style></head><body onload=""><esi:remove>
<!--
--- CUSTOMIZATION INSTRUCTIONS ---
This page is shared by both POST and GET requests. It is possible to present
different content for POST and GET requests and it is also present visually
same page to both types of requests.
POST page has a hidden HTML form tag that preserves the original customer POST.
To customize this page so that both version look the same, edit sections that
marked as CUSTOMIZE HEAD HERE or CUSTOMIZE BODY HERE.
-->
</esi:remove>
<!--<esi:vars>$add_cachebusting_header()</esi:vars>-->
<esi:comment text=" ------------- begin html ---------- ">
<!--[if IE 7]> <html class="no-js ie7 oldie" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="no-js ie8 oldie" lang="en"> <![endif]-->
<!--[if gt IE 8]><!--> <!--<![endif]-->
<esi:comment text=" --- CUSTOMIZE HEAD HERE --- ">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Hang Tight! Routing to checkout...</title>
<meta name="viewport" content="width=device-width,initial-scale=1">
<script type="text/javascript" language="JavaScript" src="./botfailoveroriginal_files/spin.min.js"></script>
<style type="text/css">
body {
margin-left: 0px;
margin-top: 0px;
margin-bottom: 0px;
margin-right: 0px;
background-color: #ffffff;
font-family: 'AvenirNextLTW02-Medium', Helvetica, Arial, Verdana, sans-serif;
color: #000000;
font-size: 100%;
background: url("/media/SPA-sitefailover/sitedownpage/images/sitedown_background.jpg") no-repeat left center fixed;
-webkit-background-size: cover;
-moz-background-size: cover;
-o-background-size: cover;
background-size: cover;
}
.top-logo {
top: 0;
left: 0;
width: 100%;
height: 100px;
background-color: red;
padding-top: 20px;
height: 41px;
background-color: white;
background-color: rgba(255, 255, 255, 0.9);
}
.top-logo img {
width: 137px;
padding-left: 67px;
}
.textholder-wrapper {
position: relative;
height: 100%;
width: 100%;
}
.textholder {
background-color: rgba(255, 255, 255, 0.8);
width: 46%;
padding: 30px;
text-align: center;
color: #020202;
font-size: 13px;
line-height: 19px;
transform: translate(0%, 11%);
left: 39%;
position: absolute;
}
h2 {
font-family: 'Avenir Next LT W02 Bold', Helvetica, Arial, Verdana, sans-serif;
font-size: 23px;
letter-spacing: 1.5px;
}
h3 {
font-size: 14px;
clear: both;
font-family:'Avenir Next W02 Light', Helvetica, Arial, Verdana, sans-serif;
padding: 0 10px;
}
table {
width: 100%;
}
.line {
position: relative;
width: 50%;
}
.line:before {
content: "";
background-color: rgba(0,0,0,0.3);
height: 1px;
width: 100%;
position: absolute;
left: 0;
top: 24px;
}
p {
font-size: 14px;
letter-spacing: 0.2px;
font-family:'Avenir Next W02 Light', Helvetica, Arial, Verdana, sans-serif;
margin-top: 0;
}
p a:link {
text-decoration: none;
color: black;
font-weight: bold;
font-family: Helvetica;
}
.eu-phones {
float: left;
width: 33%;
text-align: left;
padding-bottom: 18px;
}
.photo-credit {
position: absolute;
width: 100%;
bottom: 0;
left: 0;
font-size: 10px;
}
@media (max-width:1200px) {
.textholder {
width: 60%;
left: 28%;
}
}
@media (max-width:900px) {
.textholder {
transform: translate(0%, 4%);
}
}
@media (max-width:800px) {
.textholder {
width: 80%;
left: 6%;
transform: translate(0,0);
top: 35px;
}
}
@media (max-width:550px) {
.textholder {
transform: translate(0, 0);
left: 2%;
width: 85%;
padding: 5%;
margin-bottom: 35px;
}
.eu-phones {
margin-left: 10%;
width: 65%;
float: none;
padding-bottom: 0;
}
}
</style>
<esi:comment text=" --- STOP CUSTOMIZE HEAD HERE --- ">
<esi:comment text=" --------------- header ------------ ">
<esi:choose>
<esi:when test="$(REQUEST_METHOD)=='GET'">
<esi:comment text=" AKAMAI-UPA: GET WR page ">
<meta http-equiv="Refresh" content="30000000;URL=$(original_url)">
<esi:comment text=" css, javascript goes here ">
</esi:comment></esi:comment></esi:when>
<esi:otherwise>
<esi:comment text=" AKAMAI-UPA: POST WR page ">
<esi:comment text=" css, javascript goes here ">
</esi:comment></esi:comment></esi:otherwise>
</esi:choose>
<esi:comment text=" --- end header & start body -- part below is shared by GET and POST requests --- ">
<esi:comment text=" --- end shared body & start protocol specific body --- ">
<esi:choose>
<esi:when test="$(REQUEST_METHOD)=='GET'">
<esi:comment text=" ---------------------- GET SPECIFIC BODY ----------------------- ">
</esi:comment></esi:when>
<esi:otherwise>
<esi:comment text=" ---------------------- POST SPECIFIC BODY ----------------------- ">
<esi:comment text=" -- post body is more complex, as all data has to be replicated -- ">
<esi:vars>
<form id="wr" name="waitroomform" action="file:///Users/jreyesco/Downloads/$(original_url)" method="POST">
<esi:comment text=" -- Luhn Validation must be used to remove sensitive PCI data before storing POST body in hidden field -- ">
<esi:function name="reverse">
<esi:assign name="result" value="''">
<esi:foreach item="CHAR" collection="$(ARGS{0})">
<esi:choose>
<esi:when test="$(CHAR_start)">
<esi:assign name="result" value="$(CHAR)">
</esi:assign></esi:when>
<esi:otherwise>
<esi:assign name="result" value="$(CHAR)+$str($(result))">
</esi:assign></esi:otherwise>
</esi:choose>
</esi:foreach>
<esi:return value="$(result)">
</esi:return></esi:assign></esi:function>
<esi:function name="luhn">
<esi:assign name="reversed_cc" value="$reverse($(ARGS{0}))">
<esi:assign name="sum" value="0">
<esi:assign name="sumArray" value="[0, 2, 4, 6, 8, 1, 3, 5, 7, 9]">
<esi:foreach item="CC_DIGIT" collection="$(reversed_cc)">
<esi:choose>
<esi:when test="$(CC_DIGIT_start)">
<esi:assign name="sum" value="$int($(CC_DIGIT))">
</esi:assign></esi:when>
<esi:when test="$(CC_DIGIT_odd)">
<esi:assign name="sum" value="$int($(CC_DIGIT))+$int($(sum))">
</esi:assign></esi:when>
<esi:otherwise>
<esi:assign name="sum" value="$int($(sumArray{$int($(CC_DIGIT))}))+$int($(sum))">
</esi:assign></esi:otherwise>
</esi:choose>
</esi:foreach>
<esi:choose>
<esi:when test="$(sum)>0 && $(sum)%10==0">
<esi:return value="'true'">
</esi:return></esi:when>
<esi:otherwise>
<esi:return value="'false'">
</esi:return></esi:otherwise>
</esi:choose>
</esi:assign></esi:assign></esi:assign></esi:function>
<esi:foreach item="NAMEVALUE" collection="$(POST)">
<esi:choose>
<esi:when test="$(NAMEVALUE{0})=='submit'">
<!-- skipping submit -->
</esi:when>
<esi:when test="$(NAMEVALUE{1}) matches '''^\[\'.*?\'\]'''">
<esi:foreach item="MULTIVAL" collection="$(NAMEVALUE{1})">
<esi:assign name="IS_CC" value="'false'">
<esi:assign name="FIELD_VALUE" value="$replace($replace($(MULTIVAL), ' ', ''), '-', '')">
<esi:choose>
<esi:when test="($(FIELD_VALUE) matches '''^\d{13,16}$''' && $(QUERY_STRING{LUHN_ALGORIHTM_MODE})!='0')">
<esi:assign name="IS_CC" value="$luhn($(FIELD_VALUE))">
</esi:assign></esi:when>
</esi:choose>
<esi:choose>
<esi:when test="$(IS_CC)=='true'">
<input type="hidden" name="$(NAMEVALUE{0})" value="''">
</esi:when>
<esi:otherwise>
<input type="hidden" name="$(NAMEVALUE{0})" value="$(MULTIVAL)">
</esi:otherwise>
</esi:choose>
</esi:assign></esi:assign></esi:foreach>
</esi:when>
<esi:otherwise>
<esi:assign name="IS_CC" value="'false'">
<esi:assign name="FIELD_VALUE" value="$replace($replace($str($(NAMEVALUE{1})), ' ', ''), '-', '')">
<esi:choose>
<esi:when test="($(FIELD_VALUE) matches '''^\d{13,16}$''' && $(QUERY_STRING{LUHN_ALGORIHTM_MODE})!='0')">
<esi:assign name="IS_CC" value="$luhn($(FIELD_VALUE))">
</esi:assign></esi:when>
</esi:choose>
<esi:choose>
<esi:when test="$(IS_CC)=='true'">
<input type="hidden" name="$(NAMEVALUE{0})" value="''">
</esi:when>
<esi:otherwise>
<input type="hidden" name="$(NAMEVALUE{0})" value="$(NAMEVALUE{1})">
</esi:otherwise>
</esi:choose>
</esi:assign></esi:assign></esi:otherwise>
</esi:choose>
</esi:foreach>
<esi:choose>
<esi:when test="$int($(POST{'__wr'})) != 1">
<input type="hidden" name="__wr" value="1">
</esi:when>
</esi:choose>
<script language="JavaScript">
function submitWait() {
setTimeout('submitForm()',30000);
return(true);
}
function submitForm() {
document.waitroomform.submit();
}
</script>
</esi:comment></form></esi:vars></esi:comment></esi:comment></esi:otherwise>
</esi:choose>
<esi:comment text=" ---------------------- END PROTOCOL-SPECIFIC BODY ----------------------- ">
<esi:comment text=" --- content below is shown for both GET and POST requests --- ">
<esi:comment text=" --- CUSTOMIZE BODY HERE ---
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations258 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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+Redirect ChainNo redirects — direct accessPASS
https://www.patagonia.com
463 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.patagonia.com | 200 | 463 ms | HTTP/1.1 | AkamaiNetStorage |
A+Domain Intelligencepatagonia.com — via MarkMonitor Inc., 31 years, 6 months old, hosted on Microsoft AzurePASS
640 days
March 17, 2028
258 days
Issued by DigiCert Inc
31 years, 6 months
Registered March 16, 1995
Not enabled
Protects against DNS spoofing
Microsoft Azure
ASN AS8075
40.78.19.250
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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