Skip to content
https://www.motion.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
8 PASS 9 REVIEW
B
DNS Records
2 A records, 32 ms lookup
REVIEW
2 A records, 32 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.118.117, 104.17.119.117
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.motion.com.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 32 ms
Got: 32 ms
A104.17.118.117, 104.17.119.117
AAAA
CNAMEwww.motion.com.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 32 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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)

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 104.17.118.117: lookup 104.17.118.117: 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 104.17.119.117: lookup 104.17.119.117: 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
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
85 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

85
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f9932dc99def345-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f9932dc99def345-CDG
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 15ms across 3 resolvers (spread 26ms)
PASS
Mean 15ms across 3 resolvers (spread 26ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 68 ms total
PASS
0 redirect(s), 68 ms total

https://www.motion.com

68 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.motion.com40368 msHTTP/1.1cloudflare
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1567 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 1567 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# MI

User-agent: *

Allow: /products/brand-list$
Allow: /*/products/brand-list$
Allow: /products/custom$
Allow: /*/products/custom$
Allow: /about-mi/support-center/request-quote$
Allow: /*/about-mi/support-center/request-quote$

Allow: /orders/order-status$
Allow: /*/orders/order-status$

Disallow: /products/custom?
Disallow: /*/products/custom?
Disallow: /about-mi/support-center/request-quote?
Disallow: /*/about-mi/support-center/request-quote?

Disallow: /*?*
Disallow: /*facet_attributes.*,*
Disallow: /*facet_attributes.*facet_attributes.*facet_attributes.*
Disallow: /*category=*
Disallow: /*;sortBy=*
Disallow: /*;inStockOnly=*
Disallow: /*search;*
Disallow: /*;origin=*
Disallow: /*;q=*
Disallow: /*;sub*
Disallow: /*;for=*
Disallow: /*from=*
Disallow: /*;orderDetail=*
Disallow: /*fromSisterSite=*
Disallow: /*page=*
Disallow: /*pageNo=*
Disallow: /*numItems=*

Disallow: /*not-found*
Disallow: /*no-results*

Disallow: /dashboard
Disallow: /*/dashboard
Disallow: /auth
Disallow: /*/auth
Disallow: /checkout
Disallow: /*/checkout
Disallow: /my-account
Disallow: /*/my-account
Disallow: /orders
Disallow: /*/orders
Disallow: /register
Disallow: /*/register
Disallow: /home
Disallow: /*/home
Disallow: /login
Disallow: /*/login
Disallow: /plant-floor
Disallow: /*/plant-floor
Disallow: /verify
Disallow: /*/verify
Disallow: /saved-list
Disallow: /*/saved-list
Disallow: /signin
Disallow: /*/signin

Disallow: /*/motion3/
Disallow: /*/misvc/
Disallow: /*/configure/
Disallow: /*/build/

Sitemap: https://sitemap.motion.com/MotionIndustries_Sitemap_Root.xml

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

200https://www.motion.com/
403https://motion.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
motion.com — via GoDaddy.com, LLC, 32 years, 3 months old, hosted on Cloudflare
PASS
motion.com — via GoDaddy.com, LLC, 32 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Jul 5, 2029 (3 years, 2 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: GoDaddy.com, LLC
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: Cloudflare
Got: AS13335
Domain expiry

1147 days

July 5, 2029

SSL certificate

85 days

Issued by Google Trust Services

Domain age

32 years, 3 months

Registered July 6, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.150.42

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC
Created July 6, 1994 (32 years, 3 months ago)
Expires July 5, 2029 (3 years, 2 months)
Last Updated October 30, 2022
Name Servers ns23.domaincontrol.com, ns24.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 104.17.150.42
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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

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

Connection waterfall

DNS Lookup 70 ms TCP Connect 18 ms TLS Handshake 23 ms Server Processing 21 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://www.motion.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://www.motion.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://www.motion.com/health
Got: https://www.motion.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback