Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
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/1 IPs match cert SANREVIEW
BRedirect Chain1 redirect(s), 1709 ms totalREVIEW
https://xbiz.com
701 ms · HTTP/1.1
https://www.xbiz.com/
1007 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://xbiz.com | 301 | 701 ms | HTTP/1.1 | nginx/1.20.1 |
| 2 | https://www.xbiz.com/ | 200 | 1007 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations74 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 Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 38 ms lookupPASS
| A | 138.2.233.192 |
| AAAA | — |
| CNAME | — |
| NS | ns-1094.awsdns-08.org, ns-540.awsdns-03.net, ns-1768.awsdns-29.co.uk, ns-181.awsdns-22.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=Ca29Am-GyMwBsn_Qfv9FCFNCHI2zjpv2REQhwiWtPXA google-site-verification=tlzuhoi9MDS-qq0oVnAlD5yibKtGFMBFFJsQMwc7Dw8 SPF v=spf1 a:adnetmedia.servport.com a:mail.servport2.com include:_spf.google.com ~a... google-site-verification=y-uGv2ksvr82zs6CLCXIAZVdHOPh9zXVggpC1CIGSSc |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 23ms across 3 resolvers (spread 41ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
# XBIZ robots.txt
Sitemap: https://www.xbiz.com/sitemap.xml
Sitemap: https://www.xbiz.com/sitemap_images.xml
User-agent: *
Disallow: /pub/xbizpremiere/*
Disallow: /pub/xbizworld/*
Disallow: /pub/xbizcamworld/*
Disallow: /pub/xbizclipworld/*
Disallow: /azr94v2hh2lgbbkk/
User-agent: Scrubby
Disallow: /
User-agent: Robozilla
Disallow: /
User-agent: Gigabot
Disallow: /
User-agent: psbot
Disallow: /
User-agent: Nutch
Disallow: /
User-agent: Teoma
Disallow: /
User-agent: asterias
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: MJ12bot
Disallow: /
A+Domain Intelligencexbiz.com — via Network Solutions, LLC, 27 years, 11 months old, hosted on Oracle CloudPASS
1607 days
December 11, 2030
74 days
Issued by Let's Encrypt
27 years, 11 months
Registered December 12, 1998
Not enabled
Protects against DNS spoofing
Oracle Cloud
ASN AS31898
138.2.233.192
Network Solutions, LLC
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