Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html lang="en">
<head>
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-93RPC1X7RG"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-93RPC1X7RG');
</script>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<!-- Favicon -->
<link rel="icon" type="image/webp" href="./assets/images/business-logo.webp" />
<link rel="apple-touch-icon" href="./assets/images/business-logo.webp" />
<title>Trailzyz Private Limited | Next-Gen Software & Cloud Solutions</title>
<meta name="description"
content="Trailzyz Private Limited offers innovative software engineering, cloud integration, mobile apps, and IT solutions tailored to elevate modern businesses." />
<meta name="keywords"
content="Trailzyz Private Limited, Trailzyz, software development, cloud computing, mobile app development, IT consulting, digital transformation,cloud & cyber security" />
<!-- Open Graph / Social Media -->
<meta property="og:type" content="website" />
<meta property="og:title" content="Trailzyz Private Limited | Next-Gen Software & Cloud Solutions" />
<meta property="og:description"
content="Trailzyz Private Limited offers innovative software engineering, cloud integration, mobile apps, and IT solutions tailored to elevate modern businesses." />
<meta property="og:image" content="./assets/images/about-us-banner.webp" />
<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Trailzyz Private Limited | Next-Gen Software & Cloud Solutions" />
<meta name="twitter:description"
content="Trailzyz Private Limited offers innovative software engineering, cloud integration, mobile apps, and IT solutions tailored to elevate modern businesses." />
<meta name="twitter:image" content="./assets/images/about-us-banner.webp" />
<!-- Font -->
<link href="https://fonts.googleapis.com/css2?family=Poppins:wght@200;300;400;500;600;700&display=swap"
rel="stylesheet">
<!-- CSS -->
<link rel="stylesheet" href="./css/style.css">
<link rel="stylesheet" href="./css/animation.css">
<link rel="stylesheet" href="./css/reponsive.css">
<script type="module" crossorigin src="./assets/index-BDqlYMLS.js"></script>
<link rel="modulepreload" crossorigin href="./assets/rolldown-runtime-QTnfLwEv.js">
<link rel="modulepreload" crossorigin href="./assets/react-B9LScq2L.js">
<link rel="modulepreload" crossorigin href="./assets/gsap-CfuogOgo.js">
<link rel="modulepreload" crossorigin href="./assets/intl-DQD517rM.js">
<link rel="stylesheet" crossorigin href="./assets/intl-D_4EQVUY.css">
<link rel="stylesheet" crossorigin href="./assets/index-BwWD9bZs.css">
</head>
<body>
<div id="root"></div>
</body>
</html>
BTLS Certificate Expiry & Recommendations70 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 17 ms lookupPASS
| A | 103.189.142.88 |
| AAAA | — |
| CNAME | — |
| NS | ns39.domaincontrol.com, ns40.domaincontrol.com |
| 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 | google-site-verification=uBlpbM9C-UoyVLI40RhN8LhsoSpKHYU94RTrqnrBuYg SPF v=spf1 include:dc-aa8e722993._spfm.trailzyztech.com ~all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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 TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 27ms across 3 resolvers (spread 39ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://trailzyztech.com
714 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://trailzyztech.com | 200 | 714 ms | HTTP/1.1 | nginx/1.24.0 (Ubuntu) |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencetrailzyztech.com — via GoDaddy.com, LLC, 1 years, 10 months old, hosted on KVBPL-AS-IN - Kerala Vision Broad Band Private Limited, INPASS
1157 days
October 19, 2029
70 days
Issued by Let's Encrypt
1 years, 10 months
Registered October 19, 2024
Not enabled
Protects against DNS spoofing
KVBPL-AS-IN - Kerala Vision Broad Band Private Limited, IN
ASN AS138754
103.189.142.88
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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