Skip to content
http://mytrendyes.com

Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
6
PASS
10
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
16
10 PASS 6 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
4 PTR record(s) found (no cert data to match against)
REVIEW
4 PTR record(s) found (no cert data to match against)
Info::
PTR lookup failed for 104.21.89.110: lookup 104.21.89.110: no such host
Info::
PTR lookup failed for 172.67.140.217: lookup 172.67.140.217: no such host
Info::
PTR lookup failed for 2606:4700:3035::ac43:8cd9: lookup 2606:4700:3035::ac43:8cd9: no such host
Info::
PTR lookup failed for 2606:4700:3031::6815:596e: lookup 2606:4700:3031::6815:596e: no such host
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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 No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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: 429, /healthz: 429, /ping: 429, /status: 429.
A+
DNS Records
2 A records, 42 ms lookup
PASS
2 A records, 42 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.89.110, 172.67.140.217
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::ac43:8cd9, 2606:4700:3031::6815:596e
Info::
2 nameserver(s) configured
Got: rob.ns.cloudflare.com, meera.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 42 ms
Got: 42 ms
A104.21.89.110, 172.67.140.217
AAAA2606:4700:3035::ac43:8cd9, 2606:4700:3031::6815:596e
CNAME—
NSrob.ns.cloudflare.com, meera.ns.cloudflare.com
MX
1 smtp.secureserver.net
10 mailstore1.secureserver.net
TXT
D5536143
D1234190
SPF v=spf1 include:secureserver.net -all
CAALookup not available with standard resolver
Resolved in 42 ms
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 58ms across 3 resolvers (spread 88ms)
PASS
Mean 58ms across 3 resolvers (spread 88ms)
Info::
Quad9: 23ms
Got: 23ms via 9.9.9.9:53
Info::
Cloudflare: 42ms
Got: 42ms via 1.1.1.1:53
Info::
Google: 111ms
Got: 111ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 137 ms total
PASS
1 redirect(s), 137 ms total
Info::
Single redirect
Got: http://mytrendyes.com → https://mytrendyes.com/ (301)
Info::
HTTP to HTTPS redirect present

http://mytrendyes.com

57 ms · HTTP/1.1

301

https://mytrendyes.com/

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1http://mytrendyes.com30157 msHTTP/1.1cloudflare
2https://mytrendyes.com/42980 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3035::ac43:8cd9, 2606:4700:3031::6815:596e
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3035::ac43:8cd9, 2606:4700:3031::6815:596e Connection Reachable (17 ms)
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)

www / non-www

301http://www.mytrendyes.com/
200http://mytrendyes.com/

Preferred variant: non-www

A+
Domain Intelligence
mytrendyes.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 2 years, 3 months old
PASS
mytrendyes.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 2 years, 3 months old
Info::
Domain registered until Jul 30, 2027 (9 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: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
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.
Domain expiry

263 days

July 30, 2027

SSL certificate

No certificate data

Domain age

2 years, 3 months

Registered July 30, 2024

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::ac43:8cd9

Registrar

Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain 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 Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
Created July 30, 2024 (2 years, 3 months ago)
Expires July 30, 2027 (9 months)
Last Updated October 7, 2026
Name Servers meera.ns.cloudflare.com, rob.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3035::ac43:8cd9
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 112 ms TCP Connect 17 ms TLS Handshake 0 ms Server Processing 36 ms Content Transfer 0 ms
A
CDN & Delivery
Document on Cloudflare; assets also on Google Cloud CDN
PASS
Document on Cloudflare; assets also on Google Cloud CDN
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a51d70c889be6cdf-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Google Cloud CDN: cdn.shopify.com (assets: 15)
Got: via: 1.1 google
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 3), cache HIT
Got: cf-ray: a51d7304f91c720a-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a51d70c889be6cdf-CDG

Asset hosts on a CDN

  • cdn.shopify.com — Google Cloud CDN · assets: 15
  • cdnjs.cloudflare.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • www.googletagmanager.com — assets: 25 · Google
  • mds.oceanpayment.com — assets: 15 · not attributed
  • googleads.g.doubleclick.net — assets: 12 · Google
  • connect.facebook.net — assets: 2 · below probe threshold
  • js.shrinetheme.com — assets: 1 · below probe threshold
  • shop.app — assets: 1 · below probe threshold
  • shopify.jsdeliver.cloud — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback