Skip to content
https://decay.co.in

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 9 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.decay.co.in/
200https://decay.co.in/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://decay.co.in/

HTTP version does not redirect to HTTPS

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 149.255.58.156 does not match any cert SAN: cloud774.thundercloud.uk
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
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
68 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

68
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
C
CDN & Delivery
Action
Assets on Cloudflare (host cdn.jsdelivr.net, 7 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdn.jsdelivr.net, 7 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdn.jsdelivr.net, 7 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: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Info::
Assets on Cloudflare: cdn.jsdelivr.net (assets: 7), cache HIT
Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • cdn.jsdelivr.net — Cloudflare · assets: 7 · Cache Status: HIT

Other asset hosts

  • connect.facebook.net — 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: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 41 ms lookup
PASS
1 A records, 41 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.255.58.156
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.alisonsgroup.com, ns2.alisonsgroup.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 41 ms
Got: 41 ms
A149.255.58.156
AAAA—
CNAME—
NSns1.alisonsgroup.com, ns2.alisonsgroup.com
MX
10 mx.zoho.in
20 mx2.zoho.in
50 mx3.zoho.in
TXT
SPF v=spf1 include:zoho.in +a +mx +ip4:149.255.58.156 include:relay.thundermail.uk ~...
zoho-verification=zb82255182.zmverify.zoho.in
CAALookup not available with standard resolver
Resolved in 41 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 45ms across 3 resolvers (spread 37ms)
PASS
Mean 45ms across 3 resolvers (spread 37ms)
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 45ms
Got: 45ms via 9.9.9.9:53
Info::
Cloudflare: 64ms
Got: 64ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://decay.co.in

https://decay.co.in

260 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://decay.co.in200260 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 1752 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1752 B Sitemaps referenced 1 User-agents *, OAI-SearchBot, Claude-User, GPTBot, Perplexity-User, Google-Extended, Applebot-Extended, Meta-ExternalFetcher, Amazonbot, ClaudeBot, PerplexityBot, Meta-ExternalAgent, MistralAI-User, ChatGPT-User, Claude-SearchBot, DuckAssistBot, CCBot Blocking No — crawling allowed
# DECAY - decay.co.in
# Search engines and AI assistants are welcome. Only private and duplicate pages are kept out.

# Search engines (Google, Bing, Yandex, DuckDuckGo, Apple...)
User-agent: *
Disallow: /en/cart
Disallow: /en/checkout
Disallow: /en/buynow/
Disallow: /en/wishlist
Disallow: /en/my-account
Disallow: /en/my-orders
Disallow: /en/my-address
Disallow: /en/orders/
Disallow: /en/trackings/
Disallow: /en/guestorders/
Disallow: /en/txnsummary/
Disallow: /en/summary/
Disallow: /en/login
Disallow: /en/signup
Disallow: /en/forgot-password
Disallow: /en/change-password
Disallow: /en/product/search/
Disallow: /razorpay/
Disallow: /set-language
Disallow: /_ignition/

# AI search and assistant crawlers: ChatGPT, Claude, Perplexity, Gemini, Apple, Meta, Amazon, DuckDuckGo, Mistral, Common Crawl
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: Meta-ExternalAgent
User-agent: Meta-ExternalFetcher
User-agent: Amazonbot
User-agent: DuckAssistBot
User-agent: MistralAI-User
User-agent: CCBot
Allow: /
Disallow: /en/cart
Disallow: /en/checkout
Disallow: /en/buynow/
Disallow: /en/wishlist
Disallow: /en/my-account
Disallow: /en/my-orders
Disallow: /en/my-address
Disallow: /en/orders/
Disallow: /en/trackings/
Disallow: /en/guestorders/
Disallow: /en/txnsummary/
Disallow: /en/summary/
Disallow: /en/login
Disallow: /en/signup
Disallow: /en/forgot-password
Disallow: /en/change-password
Disallow: /en/product/search/
Disallow: /razorpay/
Disallow: /set-language
Disallow: /_ignition/

Sitemap: https://decay.co.in/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
decay.co.in — via GoDaddy, 2 years, 6 months old, hosted on AWARESOFT - Awareness Software Limited, GB
PASS
decay.co.in — via GoDaddy, 2 years, 6 months old, hosted on AWARESOFT - Awareness Software Limited, GB
Info::
Domain registered until May 8, 2027 (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: GoDaddy
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: AWARESOFT - Awareness Software Limited, GB
Got: AS34931
Domain expiry

177 days

May 8, 2027

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

2 years, 6 months

Registered May 8, 2024

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWARESOFT - Awareness Software Limited, GB

ASN AS34931

149.255.58.156

Registrar

GoDaddy

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
Created May 8, 2024 (2 years, 6 months ago)
Expires May 8, 2027 (5 months)
Last Updated June 22, 2026
Name Servers ns0.thundercloud.uk, ns1.thundercloud.uk
DNSSEC Not enabled
Hosting
IP Address 149.255.58.156
ASN AS34931 (AWARESOFT - Awareness Software Limited, GB)
Provider AWARESOFT - Awareness Software Limited, GB
Data source: rdap (0.7s)

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

Connection waterfall

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

Send Feedback