Infrastructure
· 9 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.
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations240 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
A+DNS Records1 A records, 58 ms lookupPASS
| A | 23.37.169.205 |
| AAAA | 2a02:26f0:1380:2b7::24e8, 2a02:26f0:1380:29a::24e8 |
| CNAME | — |
| NS | a4-64.akam.net, a3-67.akam.net, a1-18.akam.net, a26-66.akam.net, a7-65.akam.net, a2-65.akam.net |
| MX | 0 ndtv-com.mail.protection.outlook.com |
| TXT | logmein-verification-code=Hyu9BgeCevw9kxEaVjQJPdD4e SPF v=spf1 a mx a:hybrid1.archana.ndtv.com a:hybrid2.archana.ndtv.com ip4:103.55.184... _mp36h3qxgz4nmy28nsxop8vb17shfq7 google-site-verification=wMx33zb4Zw-PtJHiD8LIVhgrwGQauMZKxchmNKDHg9A openai-domain-verification=dv-MMppIFptrp0RAip5fJq8y2qr google-site-verification=Umm0fKybZQZ8XxUN-vqFxZZYm_dGambIyYklnwvTXVg teamviewer-sso-verification=96740100912c4c569f7ff5104092eaf3 zUr4MQ2YdwvW9prR8JwB8VhUz4jo5/i960GWQgaQ88Coeb/xRsoknsZgAWpc2A42oLKzZcxwr6wF68Gh... google-site-verification=8uCnZWP_G038xSpMzMxb9mfGPqVUEm0VIyK50zL3Bmg google-gws-recovery-domain-verification=41740344 google-site-verification=Ul0ggidmOE1WiebhIrmu19Lmb76NMlEwZKhSHcE3Tfs e140759083084f1da68eb785e00e3ef7 google-site-verification=_R6y-iRrKBL0Oabu_gVlpCLOcuJmfX7NU-JDToxjxKs Google-site-verification=1HQQ2a3IDDFMTM4e9bWx7vrSDukxABnAC4jz7bFny7g google-site-verification=vUr7fa4lYc7tByPeFlYRHobzxAwfb2_j2TtfwOfpFUA bs1w58k7qlg187y0nf0gvgpl6nrp5s4g |
| 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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 47 ms totalPASS
https://ndtv.com
7 ms · HTTP/1.1
https://www.ndtv.com/
41 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ndtv.com | 301 | 7 ms | HTTP/1.1 | |
| 2 | https://www.ndtv.com/ | 403 | 41 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencendtv.com — via Network Solutions, LLC, 29 years, 11 months oldPASS
2266 days
September 25, 2032
240 days
Issued by DigiCert Inc
29 years, 11 months
Registered September 26, 1996
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1380:2b7::24e8
Network Solutions, 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