Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations51 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 55 ms lookupPASS
| A | 104.18.8.70, 104.18.9.70 |
| AAAA | 2606:4700::6812:946, 2606:4700::6812:846 |
| CNAME | — |
| NS | aragorn.ns.cloudflare.com, kristin.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com |
| TXT | MS=68C40BCD533DEAD910ED6D75A8EA2CC692830278 atlassian-domain-verification=2aqRUBaHlTxaThE984oqhEl/jHNJ7WBEcTgGutZmeNYdc9y1GC... atlassian-domain-verification=V0LkT94UZIHLcia33fEkUARU1FhFu0S9a3FZFQDis9yc13lJ3g... c43ng4mck664xbldz84x01v148g4qfg8 google-site-verification=-ibwX7X44qQrlu2DjA4XqhrH3I8Q1eKnbQwF_lrj6Gc google-site-verification=3lU52RyVZOha0xkRb1JfoJOGjFrC3cQYHlv_6kBa9Bo google-site-verification=EImkJBDGaJQNaXwde2Lmr860ybdRTMH5aYnyzh-IFI0 google-site-verification=NFOdkNMAq0KSFfDn9dhJFAzNPCtZuQAwQab9l5XDGrw google-site-verification=WddBPo_2Ibm_KCN8cfyYXkjlRQM1x6mditiA8gmyXAQ google-site-verification=efp-xTvkocf2V5xhMKP3PEw5bG09zxFUcp-oY9m03Zk google-site-verification=fPWyoD4kdVSi6sWbejOxnJ6j6YQLLbcL9G8RAgV_8kw google-site-verification=nYhpHUSldGlu0S3B8kW-JHF3MFS4Ezq8XIF57AdfgjA mixpanel-domain-verify=9b46f0c7-a390-4f5a-8fe5-6d67c766674c postman-domain-verification=97c493b17bc0fa06a6c000e0f366760049a6c9641c583f770614... sending_domain999441=b2f033ff9c16e3e375548933cd8893ecb90c2243021e60bfab1bcc6ad1c... stripe-verification=8a1d92e0ee6799c9a48076846239220cb0b8117b53bbbb309f0a32f17f44... SPF v=spf1 a:mt11.marinetraffic.com include:_spf.google.com include:sparkpostmail.co... y2gmjlt81m3kbc9qc24lbdx1ssc07324 |
| 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), 50 ms totalPASS
https://marinetraffic.com
22 ms · HTTP/1.1
https://www.marinetraffic.com/
27 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://marinetraffic.com | 302 | 22 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.marinetraffic.com/ | 200 | 27 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
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
# As a condition of accessing this website, you agree to abide by the following
# content signals:
# (a) If a Content-Signal = yes, you may collect content for the corresponding
# use.
# (b) If a Content-Signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a Content-Signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via Content-Signal with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from your website's contents). Search does not
# include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of content for
# generative AI search answers).
# ai-train: training or fine-tuning AI models.
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# BEGIN Cloudflare Managed content
User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /
User-agent: Amazonbot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: CloudflareBrowserRenderingCrawler
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: meta-externalagent
Disallow: /
# END Cloudflare Managed Content
A+Domain Intelligencemarinetraffic.com — via Name.com, Inc., 18 years, 8 months oldPASS
840 days
November 4, 2028
51 days
Issued by Google Trust Services
18 years, 8 months
Registered November 4, 2007
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:946
Name.com, 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