Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
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
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
#
# robots.txt for https://www.macrotrends.net
#
# Block various useless bots from crawling the site
User-agent: ChatGPT-User
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: rogerbot
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: DataForSeoBot
Disallow: /
User-agent: BomboraBot
Disallow: /
User-agent: BLEXBot
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: YandexBot
Disallow: /
User-agent: Yeti
Disallow: /
User-agent: Turnitin
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: academicbot
Disallow: /
User-agent: coccocbot
Disallow: /
User-agent: YouBot
Disallow: /
User-agent: SeznamBot
Disallow: /
User-agent: AwarioSmartBot
Disallow: /
User-agent: MicroAdBot
Disallow: /
User-agent: MojeekBot
Disallow: /
User-agent: Barkrowler
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: Qwarrybot
Disallow: /
User-agent: Discordbot
Disallow: /
User-agent: Exabot
Disallow: /
User-agent: *
Disallow: /stock-comparison
Disallow: /search/
Disallow: /series/
Disallow: /test/
Disallow: /dev/
Disallow: /sandbox/
Disallow: /pma/
Disallow: /stats/
Disallow: /Secure_Server/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations89 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 & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 5 ms lookupPASS
| A | 172.66.160.233, 104.20.41.172 |
| AAAA | 2606:4700:10::6814:29ac, 2606:4700:10::ac42:a0e9 |
| CNAME | — |
| NS | ezra.ns.cloudflare.com, tani.ns.cloudflare.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 | g3fjw2xbhdbhrs3bt05cggrylh9fxqjk google-site-verification=d5bY_A2sQ7hXFYmwrjs7rXIP11auFSAeRGmKB3D-wP8 SPF v=spf1 include:spf.mailjet.com ?all |
| 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), 59 ms totalPASS
https://macrotrends.net
21 ms · HTTP/1.1
https://www.macrotrends.net/
38 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://macrotrends.net | 301 | 21 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.macrotrends.net/ | 200 | 38 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligencemacrotrends.net — via Cloudflare, Inc., 13 years, 2 months oldPASS
305 days
April 17, 2027
89 days
Issued by Google Trust Services
13 years, 2 months
Registered April 17, 2013
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::6814:29ac
Cloudflare, Inc.
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