Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations72 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, 40 ms lookupPASS
| A | 104.18.40.227, 172.64.147.29 |
| AAAA | 2606:4700:4402::6812:28e3, 2a06:98c1:3105::ac40:931d |
| CNAME | — |
| NS | chip.ns.cloudflare.com, athena.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | 9d41dd32df50d1aaf81e093200991ca2 SPF v=spf1 a ip4:166.78.238.159 ip6:2001:4801:7819:74:d007:6caf:ff10:35d9 include:_s... google-site-verification=mUap3X_e_NQGZOaAfDOMHREaGj_r8EGWBMhh5wWod8k |
| 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), 286 ms totalPASS
https://business2community.com
70 ms · HTTP/1.1
https://www.business2community.com/
216 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://business2community.com | 301 | 70 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.business2community.com/ | 200 | 216 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
# This virtual robots.txt file was created by the Virtual Robots.txt WordPress plugin: https://www.wordpress.org/plugins/pc-robotstxt/
Sitemap: https://www.business2community.com/sitemap_index.xml
User-agent: *
Disallow: /stockade.php
Disallow: /cgi-bin/
Disallow: */wp-admin
Disallow: /trackback/
Disallow: /xmlrpc.php
Disallow: */search/
Disallow: *content_title
Disallow: /visit/
Disallow: */visit/
Disallow: */in-content-providers/
User-agent: Qwantify
Disallow: /
A+Domain Intelligencebusiness2community.com — via SafeNames Ltd., 15 years, 6 months oldPASS
574 days
January 10, 2028
72 days
Issued by Google Trust Services
15 years, 6 months
Registered January 10, 2011
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:4402::6812:28e3
SafeNames Ltd.
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