Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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
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 & Recommendations33 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, 39 ms lookupPASS
| A | 104.18.39.152, 172.64.148.104 |
| AAAA | — |
| CNAME | — |
| NS | ns1.markmonitor.com, ns5.markmonitor.com, ns7.markmonitor.com, ns3.markmonitor.com, ns6.markmonitor.com, ha2.markmonitor.zone, ns2.markmonitor.com, ns4.markmonitor.com, ha4.markmonitor.zone |
| MX | 0 markmonitor-com.mail.eo.outlook.com |
| TXT | google-site-verification=GZUp3F-aoKxu2bX09NyuMPTi-LXAC-qID0GhrRmddog webexdomainverification.5523f43614297acbe053ab06fc0a5471=b0c2366e-7287-438d-af3f... pardot1105752=05d648070e9b5bbc55dad335bec3d2686884b760e15145b02655f8b1fbc275e0 0DuNVXCw+Ru0wk/l1QQLpIrBqVp0lV/Sq6AYcat5UGoDXbEm3DJi3zGniT7Yc70rlPXm/L96RJ7ZUSH9... MS=ms64044723 knowbe4-site-verification=2196cd8a72de50eedd7703120b752b77 MS=ms72445593 SPF v=spf1 include:spf1.markmonitor.com include:spf2.markmonitor.com -all onetrust-domain-verification=8fa95c5bed48415db6eff59daea56015 google-site-verification=avfMNTcfZbndF_OIvDLsN68e2gYdCy3NWlLmimTCgzQ google-site-verification=E2u1YzHLf2tBYBPtKA53nJJU8CxqvETi9tCgrStrHSE MS=ms42144968 logmein-verification-code=ANmgyb4yoduCdzD71JRmCSyp2 |
| 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), 175 ms totalPASS
https://markmonitor.com
68 ms · HTTP/1.1
https://www.markmonitor.com/
107 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://markmonitor.com | 302 | 68 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.markmonitor.com/ | 403 | 107 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
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencemarkmonitor.com — via MarkMonitor Inc., 27 years, 4 months old, hosted on CloudflarePASS
2110 days
April 23, 2032
33 days
Issued by DigiCert Inc
27 years, 4 months
Registered April 23, 1999
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.39.152
MarkMonitor 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