Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations77 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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records2 A records, 38 ms lookupPASS
| A | 172.64.152.90, 104.18.35.166 |
| AAAA | 2606:4700:4408::ac40:985a, 2a06:98c1:3109::6812:23a6 |
| CNAME | — |
| NS | ivy.ns.cloudflare.com, arnold.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com |
| TXT | google-site-verification=7qQXMtBpwY4-G9zXCIxQOyn2tZAJswwFmIxKrv-O8V8 SPF v=spf1 include:sendgrid.net ~all google-site-verification=2iMJcOunPqFjV9S-aJ3mqYsWTE5oM_pQYi20x4WGwuY google-site-verification=bJFlxY62kpfPVuyIqYpprlvyom-h_VaxiKXSOv2XBE0 |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 23ms across 3 resolvers (spread 9ms)PASS
ARedirect Chain1 redirect(s), 267 ms totalPASS
https://teamskeet.com
76 ms · HTTP/1.1
https://www.teamskeet.com/
191 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://teamskeet.com | 301 | 76 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.teamskeet.com/ | 200 | 191 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 18733 URLsPASS
User-agent: *
Allow: /
Sitemap: https://www.teamskeet.com/sitemap.xml
A+Domain Intelligenceteamskeet.com — via NameCheap, Inc., 19 years, 3 months oldPASS
363 days
August 16, 2027
77 days
Issued by Google Trust Services
19 years, 3 months
Registered August 16, 2007
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:4408::ac40:985a
NameCheap, 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