Skip to content
https://houzz.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 3978 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 3978 B Sitemaps referenced 0 User-agents OAI-SearchBot, Claude-User, Google-Extended, *, AdsBot-Google, GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Twitterbot, AdsBot-Google-Mobile Blocking No — crawling allowed
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: PerplexityBot
User-agent: Claude-User
User-agent: Google-Extended
Allow: /hznb/projects/
Disallow: /hznb/projects/*?from=
User-Agent: *
Disallow: /ad/*
Disallow: /discussions/*sort=*
Disallow: /discussions/*view=*
Disallow: /proMatch/*
Disallow: /writeReview/cmd=*
Disallow: /writeReview2/cmd=*
Disallow: /writeReview2/ew
Disallow: /sketches/
Disallow: */badges/*
Disallow: /imageClipperUpload*
Disallow: /edit/*
Disallow: /*/tag=*
Disallow: /pro2/*
Disallow: /*spf=*
Disallow: /trk/*
Disallow: /hsc/*
Disallow: *jsGalleryWidget
Disallow: *reviewWidget
Disallow: /feed/
Disallow: /activities/
Disallow: /proMatch/
Disallow: */user/
Disallow: /pro-site/
Disallow: /serviceQuestionnaireAjax
Disallow: /siteSwitch
Disallow: /projects/
Disallow: /proProjects/
Disallow: /browseReviews
Disallow: /error/
Disallow: /reviewSeller
Disallow: /houzz-historyzz
Disallow: /j/pro-site
Disallow: /http
Disallow: /thumbs/

#marketing
Disallow: /builders/
Disallow: /designers/
Disallow: /pro-meeting/
Disallow: /estimates/*/client
Disallow: /manage/leads/

#internal
Disallow: /grow/
Disallow: /settings/
Disallow: /manage/
Disallow: /pro-meeting/
Disallow: /lead-form/
Disallow: /editProfile/
Disallow: /estimates/
Disallow: /visual-tools/
Disallow: /builders/
Disallow: /designers/

# CMS search pages
Disallow: /pro-learn/s/
Disallow: /pro-help/q/

# Scholarship Pages
Disallow: /scholarships
Disallow: *scholarship

#block buttonWidget and imageClipperUpload
Disallow: *buttonWidget
Disallow: *imageClipperUpload
Disallow: *proVideoWidget

#facets
Disallow: /photos/*a_86-
Disallow: *phbr*_template_
Allow: *phbr0
Allow: *phbr1-
Disallow: *phbr
Allow: *prbr0
Allow: *prbr1
Disallow: *prbr
Disallow: *phbr~r_
Disallow: *probr*_template_
Allow: */probr-1~/project-type--*/$
Disallow: */professionals/*/*project-type-*-probr1-*_template_
Allow: */professionals/*/*project-type-*-probr1-*
Allow: *probr0*
Disallow: *probr*

#query/search pages
Disallow: */query/*
Disallow: /professionals/*/s/
Disallow: /professionals/s/
Disallow: /s/*
Disallow: */searchDirectory
Disallow: /professionals/query*
Disallow: *query=
Disallow: *nqrwns
Allow: /products/query/
Allow: /photos/query/
Disallow: /products/query/*nqrwns
Disallow: *?oq=

#email
Disallow: *OptOutEmail*
Disallow: *optInEmail*

#old pages
Disallow: /js/widget.js*
Disallow: /js/ajaxconn*
Disallow: *jsErrAjax
Disallow: *uiLoggerAjax

#sort filters
Disallow: /*/live-stream/
Disallow: /*/popular-today/
Disallow: /*/popular/
Disallow: /*/avg-review/
Disallow: /professionals/*/sortReviews

#view filters
Disallow: */ls=

#pros
Disallow: /organizationMembers/

#Reviews
Disallow: /viewReview/

#bots
Disallow: *hznb*
Disallow: /getMoreSimilarGalleriesAjax

#legacy
Disallow: /sw$
Disallow: /uk$
Disallow: /au$
Disallow: /de$
Disallow: /fr$
Disallow: /ru$
Disallow: /gws$
Disallow: /ie$
Disallow: /nz$
Disallow: /sg$
Disallow: /in$
Disallow: /se$
Disallow: /jp$
Disallow: /es$
Disallow: /it$
Disallow: /dk$
Disallow: /sw/
Disallow: /uk/
Disallow: /au/
Disallow: /de/
Disallow: /fr/
Disallow: /ru/
Disallow: /ie/
Disallow: /nz/
Disallow: /sg/
Disallow: /in/
Disallow: /se/
Disallow: /jp/
Disallow: /es/
Disallow: /it/
Disallow: /dk/
Disallow: /*/s/*
Disallow: /*/vendorActivityManager/*

#cobrands
Disallow: *?cbp

#ideabooks
Disallow: */list/*
Disallow: */plans/*
Allow: /products/holiday-sales-*sgbr-sg*
Disallow: *sgbr-sg

#old pages
Allow: /pro-learn/blog/*error*
Disallow: /get-hired/
Disallow: /fbhome
Disallow: *error*

#twitter
User-Agent: Twitterbot
Allow: *sgbr-sg
Allow: *phvw-vp
Allow: /magazine/
Allow: /ideabooks/
Allow: /pro-learn/
Disallow: /discussions/*/p/_template_
Allow: /discussions/
Disallow: /

#other
Disallow: *_template
Disallow: *?null

Allow: /

#adsbot
User-agent: AdsBot-Google
User-agent: AdsBot-Google-Mobile
Disallow: /js/widget.js*
Disallow: /js/ajaxconn*
Disallow: *jsErrAjax
Disallow: *uiLoggerAjax

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.houzz.com/
200https://houzz.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://houzz.com/ https://www.houzz.com/

Consistent

B
TLS Certificate Expiry & Recommendations
97 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
4 A records, 61 ms lookup
PASS
4 A records, 61 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.0.93, 151.101.192.93, 151.101.128.93, 151.101.64.93
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1918.awsdns-47.co.uk, ns-1203.awsdns-22.org, ns-361.awsdns-45.com, ns-907.awsdns-49.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: 61 ms
Got: 61 ms
A151.101.0.93, 151.101.192.93, 151.101.128.93, 151.101.64.93
AAAA
CNAME
NSns-1918.awsdns-47.co.uk, ns-1203.awsdns-22.org, ns-361.awsdns-45.com, ns-907.awsdns-49.net
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt3.aspmx.l.google.com
30 alt4.aspmx.l.google.com
TXT
orbitid-domain-verification=clpsq9e5n7096bjotcslasa6s:houzz.com
7da3f610-9d66-4d7c-8109-6fb8214eb731
apple-domain-verification=0CxrY6eip6DEGmIN
stripe-verification=3A703499C2EF1B7726B540AC792D773DF3F60BC49ED4CF260422986E9422...
MS=ms37417764
_globalsign-domain-verification=JpB77KoCfbn-ws0kn1vpt10A6CBtJgH--nNHhMqDQe
mgverify=01ccca75efe1499bb7530db04458920a8328ee423523efd16f6bb8159045c19f
stripe-verification=F83B26205B00BD3537639D1BBE2E58961FA20B719E9843AF775FB9C3AE9B...
stripe-verification=2b6a4300270d8547fc472782a52e3536d26d1e3377f58b7d715dcf4db791...
openai-domain-verification=dv-7lGFWVShTI1J4w5BWoV0KEUW
ZOOM_verify_dSOhOFUlQGCHYpjgO6aDOg
adobe-idp-site-verification=f11aed2309a6d56ed8bc284ec4a5aeed5f5687bed022155b83d0...
SPF v=spf1 include:spf.houzz.com include:_spf.google.com include:servers.mcsv.net in...
_globalsign-domain-verification=WordA2Sf_KSU4wD9aLhJ43E07uuoFkVeNCh8dAygSn
_globalsign-domain-verification=KXD5_ZtogrSwNp0hc4NLLJN_MSqsaRDfdEq3k42nQa
cursor-domain-verification-6z27vb=TaesMoz4OEIR3ICFZU0qiWkCv
wrike-verification=MjYxMDU1Mjo0MmEyNTk0NDFlMmUxMzZmYWQzYmYxYTA1Y2EwMTU0MzdjMmE1Y...
stripe-verification=da9c68d1fbd517f10205eb9bad43f895ec615446314cc3d2c94648ed44d1...
remote-domain-verification=5d698be2-85bd-461c-a84c-eefdef78d454
google-site-verification=36FsI2ejufUIhQy7Lv9zQTiUWV6JAuut7RGRB5A_Qjg
16BA3A0BB6
_globalsign-domain-verification=lFg4iNLqd9WfeKuRGbw4wSeB5G0sJ3z8RIhcXYl_05
atlassian-domain-verification=PKfa9x4PSgPna1TisNIyVarS94fNiv/vKxiUYLoyrfZ/mwwyKD...
anthropic-domain-verification-3gj4fm=Ob8u8z9GsTTTAOLmA3WpMBGnA
google-site-verification=kXZ58MSj4K4zD2i-AjJr2OWIYWCPxeSNzEOEVM2wHlM
CAALookup not available with standard resolver
Resolved in 61 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
1 redirect(s), 795 ms total
PASS
1 redirect(s), 795 ms total
Info::
Single redirect
Got: https://houzz.com → https://www.houzz.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 795 ms total
Got: 795 ms

https://houzz.com

4 ms · HTTP/1.1

301

https://www.houzz.com/

791 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://houzz.com3014 msHTTP/1.1
2https://www.houzz.com/200791 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
houzz.com — via CSC Corporate Domains, Inc., 19 years, 9 months old, hosted on Fastly
PASS
houzz.com — via CSC Corporate Domains, Inc., 19 years, 9 months old, hosted on Fastly
Info::
Domain registered until Oct 29, 2026 (6 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: CSC Corporate Domains, 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: Fastly
Got: AS54113
Domain expiry

105 days

October 29, 2026

SSL certificate

97 days

Issued by GlobalSign nv-sa

Domain age

19 years, 9 months

Registered October 29, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.128.93

Registrar

CSC Corporate Domains, 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 CSC Corporate Domains, Inc.
Created October 29, 2006 (19 years, 9 months ago)
Expires October 29, 2026 (6 months)
Last Updated October 25, 2025
Name Servers ns-1203.awsdns-22.org, ns-1918.awsdns-47.co.uk, ns-361.awsdns-45.com, ns-907.awsdns-49.net
DNSSEC Not enabled
Hosting
IP Address 151.101.128.93
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.4s)

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

A+
HTTP Probe Timing
Total 33 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
34 ms
Total Time Total request time from DNS lookup through full response.
34 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 1 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback