Skip to content
https://smartthings.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 251 ms total
REVIEW
2 redirect(s), 251 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://smartthings.com

126 ms · HTTP/1.1

301

https://www.smartthings.com/

71 ms · HTTP/1.1

301

https://www.samsung.com/us/smartthings/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://smartthings.com301126 msHTTP/1.1CloudFront
2https://www.smartthings.com/30171 msHTTP/1.1CloudFront
3https://www.samsung.com/us/smartthings/20054 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
243 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

243
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
B
CDN & Delivery
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU3-P12)
Got: x-amz-cf-id: cu0ZIEPQlrp_2iTtbtk1Fd9RZPK0lg4pgzavXe7e8_C58HFFA4SUGA==
Info::
CDN cache status: LambdaGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: cu0ZIEPQlrp_2iTtbtk1Fd9RZPK0lg4pgzavXe7e8_C58HFFA4SUGA==
A+
DNS Records
4 A records, 90 ms lookup
PASS
4 A records, 90 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.227.207.54, 13.227.207.91, 13.227.207.31, 13.227.207.17
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1275.awsdns-31.org, ns-1610.awsdns-09.co.uk, ns-442.awsdns-55.com, ns-779.awsdns-33.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: 90 ms
Got: 90 ms
A13.227.207.54, 13.227.207.91, 13.227.207.31, 13.227.207.17
AAAA
CNAME
NSns-1275.awsdns-31.org, ns-1610.awsdns-09.co.uk, ns-442.awsdns-55.com, ns-779.awsdns-33.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
amazonses:Q67mtfR398MNBLeoVTPTryS7buA2T0kDpOKMPY80OTI=
apple-domain-verification=FhkfJ8985Dxxcq8C
atlassian-domain-verification=YFZR4asBfP56Kq3VVYn5BYlBVCEvQkJOY/rwBvV5RW4L1mi6fM...
bugcrowd-verification=22a127ca61489af474995aab9d112594
docker-verification=68de28df-81cd-4c04-8944-da89b56a25ff
google-site-verification=Qj2lesjIqvDavthiEN-l6gbC3o0J72-7wgLTkj4FjCY
google-site-verification=zuRbJ1lBtF1KRJdhTm5ANxFgaS-chF01EOBgZ8xYN0Q
include:amazonses.com
launchdarkly-domain-verification=335c7a61-ddbf-404f-979a-6f9ffb6d4830
onetrust-domain-verification=456c40a36244473da190bbd2499842ca
openai-domain-verification=dv-v1lBqcrnA1jycYR0wWJE2PWg
sending_domain1077393=b6a4ad3db7e8013c942cb1c3810855b1b99b9e8870e25711b2b6ff55f3...
status-page-domain-verification=mk75zb5v5zlf
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:_spf.atlassian.n...
zoom-domain-verification = e9749fdf-2713-4d42-ae73-72ed49e0e918
CAALookup not available with standard resolver
Resolved in 90 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+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 122 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 122 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://partners.smartthings.com/sitemap-index.xml
Host: https://partners.smartthings.com

sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.smartthings.com/
200https://smartthings.com/

Preferred variant: non-www

HTTP → HTTPS

301http://smartthings.com/ https://smartthings.com/

Consistent

A+
Domain Intelligence
smartthings.com — via MarkMonitor Inc., 22 years, 10 months old, hosted on AWS
PASS
smartthings.com — via MarkMonitor Inc., 22 years, 10 months old, hosted on AWS
Info::
Domain registered until Sep 30, 2027 (1 years, 5 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

445 days

September 30, 2027

SSL certificate

243 days

Issued by Amazon

Domain age

22 years, 10 months

Registered September 30, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.227.207.91

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 September 30, 2003 (22 years, 10 months ago)
Expires September 30, 2027 (1 years, 5 months)
Last Updated August 29, 2025
Name Servers ns-1275.awsdns-31.org, ns-1610.awsdns-09.co.uk, ns-442.awsdns-55.com, ns-779.awsdns-33.net
DNSSEC Not enabled
Hosting
IP Address 13.227.207.91
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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 52 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
53 ms
Total Time Total request time from DNS lookup through full response.
53 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 23 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