Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
CMulti-Resolver DNS SpeedActionMean 130ms across 3 resolvers (spread 206ms)REVIEW
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
CTLS Certificate Expiry & RecommendationsAction28 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 28 days remaining
- 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 Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records2 A records, 324 ms lookupPASS
| A | 91.108.127.19, 147.79.105.32 |
| AAAA | 2a02:4780:84:d932:f341:cd2:147d:77cc, 2a02:4780:84:380d:cb1c:d1b1:d2aa:5409 |
| CNAME | — |
| NS | ns1.dns-parking.com, ns2.dns-parking.com |
| MX | 10 mx.zoho.eu 20 mx2.zoho.eu 50 mx3.zoho.eu |
| TXT | SPF v=spf1 include:zohomail.eu include:_spf.mail.hostinger.com ~all |
| CAA | Lookup not available with standard resolver |
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Redirect ChainNo redirects — direct accessPASS
https://vendixdesigns.com
429 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://vendixdesigns.com | 200 | 429 ms | HTTP/1.1 | hcdn |
A+IPv6 ReadinessIPv6 reachable (3 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
User-agent: *
Allow: /
Sitemap: https://vendixdesigns.com/sitemap.xml
A+Domain Intelligencevendixdesigns.com — via GoDaddy.com, LLC, 3 years, 2 months oldPASS
311 days
September 1, 2027
28 days
Issued by Let's Encrypt
3 years, 2 months
Registered September 1, 2023
Not enabled
Protects against DNS spoofing
Unknown
2a02:4780:84:e9fc:f49c:d7ca:b6c3:3ce1
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- 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