Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations48 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryAkamaiREVIEW
A+DNS Records2 A records, 30 ms lookupPASS
| A | 2.20.71.228, 2.20.71.230 |
| AAAA | 2a02:26f0:1380:27::5f64:6d5d, 2a02:26f0:1380:27::5f64:6d56 |
| CNAME | — |
| NS | a28-65.akam.net, a5-66.akam.net, a8-67.akam.net, a11-67.akam.net, a1-142.akam.net, a14-64.akam.net |
| MX | 10 mx1.hc1534-53.ap.iphmx.com 10 mx2.hc1534-53.ap.iphmx.com |
| TXT | 2qjkj20cvocctjm4n9r350cu0i MS=ms40236505 SPF v=spf1 exists:%{i}.spf.hc1534-53.ap.iphmx.com include:moneycontroltoday.com incl... google-site-verification=9O5Kqj_HJ7XhMkJAN4A2r9SquVnGkmjFFiUcYhuRUug _hwu86ztv5dz9tpgh3lmoco1lw1twqtp google-site-verification=EkMYoWUzn1kPe_0MB2IGEd0aKZTEygP2t6DRR_wlLec google-site-verification=4o8sgzr4evR1Q0naFI1gpfs55uw01kpqlkjDidBHhOY shigrkr4urcadi37jo3o844v8k _w1govba1k6jcpo04is71k58qchum2pe g4upagvib4kgtq48d9pe9v6hir bs467kopqnhcmp3trretepudju MS=ms48964266 |
| CAA | Lookup not available with standard resolver |
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), 61 ms totalPASS
https://moneycontrol.com
19 ms · HTTP/1.1
https://www.moneycontrol.com/
41 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://moneycontrol.com | 301 | 19 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.moneycontrol.com/ | 403 | 41 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencemoneycontrol.com — via PDR Ltd. d/b/a PublicDomainRegistry.com, 27 years, 6 months oldPASS
1320 days
February 28, 2030
48 days
Issued by Let's Encrypt
27 years, 6 months
Registered February 28, 1999
Enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1380:27::5f64:6d56
PDR Ltd. d/b/a PublicDomainRegistry.com
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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