Skip to content
https://www.motolink.sa/ar

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
12
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 12 REVIEW
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 185.196.101.232 does not match any cert SAN: alphacapitalsy.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
Multi-Resolver DNS Speed
Action
Mean 183ms across 3 resolvers (spread 297ms)
REVIEW
Mean 183ms across 3 resolvers (spread 297ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 214ms
Got: 214ms via 9.9.9.9:53
Info::
Cloudflare: 317ms
Got: 317ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 297ms (min 20ms / max 317ms)
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 24 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 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Connection waterfall

DNS Lookup 343 ms TCP Connect 48 ms TLS Handshake 77 ms Server Processing 493 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
78 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

78
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
C
CDN & Delivery
Action
Assets on Cloudflare (host unpkg.com, 3 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host unpkg.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (unpkg.com, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a5643bf97c822a22-CDG
Info::
Assets on Cloudflare: unpkg.com (assets: 3), cache HIT
Got: cf-ray: a5643bf97c822a22-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • unpkg.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • cdn.jsdelivr.net — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 128 ms lookup
PASS
1 A records, 128 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.196.101.232
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
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: motolink.sa
Info::
4 nameserver(s) configured
Got: dns4.supremepanel.com, dns1.supremepanel.com, dns3.supremepanel.com, dns2.supremepanel.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 128 ms
Got: 128 ms
A185.196.101.232
AAAA—
CNAMEmotolink.sa
NSdns4.supremepanel.com, dns1.supremepanel.com, dns3.supremepanel.com, dns2.supremepanel.com
MX
0 motolink.sa
TXT
SPF v=spf1 +a +mx +ip4:185.196.101.100 ~all
CAALookup not available with standard resolver
Resolved in 128 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

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

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.motolink.sa/ar

https://www.motolink.sa/ar

644 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.motolink.sa/ar200644 msHTTP/1.1LiteSpeed
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: www)
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

200https://www.motolink.sa/ar
301https://motolink.sa/ar

Preferred variant: www

Trailing Slash

301https://www.motolink.sa/ar/
200https://www.motolink.sa/ar

HTTP → HTTPS

302http://www.motolink.sa/ar → https://www.motolink.sa/ar

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
motolink.sa — hosted on belcloud - Belcloud LTD, BG
PASS
motolink.sa — hosted on belcloud - Belcloud LTD, BG
Info::
Hosting: belcloud - Belcloud LTD, BG
Got: AS44901
Domain expiry

Unknown

SSL certificate

78 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

belcloud - Belcloud LTD, BG

ASN AS44901

185.196.101.232

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Name Servers dns1.supremepanel.com, dns2.supremepanel.com
Hosting
IP Address 185.196.101.232
ASN AS44901 (belcloud - Belcloud LTD, BG)
Provider belcloud - Belcloud LTD, BG
Data source: whois (1.6s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback