Skip to content
https://xoilackq.tv

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

86
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9f07fec5efcea426-GRU
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07fec5efcea426-GRU
A+
DNS Records
2 A records, 22 ms lookup
PASS
2 A records, 22 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.18.37, 104.18.19.37
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1325, 2606:4700::6812:1225
Info::
2 nameserver(s) configured
Got: craig.ns.cloudflare.com, sandra.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 22 ms
Got: 22 ms
A104.18.18.37, 104.18.19.37
AAAA2606:4700::6812:1325, 2606:4700::6812:1225
CNAME—
NScraig.ns.cloudflare.com, sandra.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 22 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 567 ms total
PASS
1 redirect(s), 567 ms total
Info::
Single redirect
Got: https://xoilackq.tv → https://xoilackv.tv/ (301)
Info::
Redirect overhead: 567 ms total
Got: 567 ms
Info::
Cross-domain redirect detected

https://xoilackq.tv

27 ms · HTTP/1.1

301

https://xoilackv.tv/

540 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://xoilackq.tv30127 msHTTP/1.1cloudflare
2https://xoilackv.tv/200540 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:1325, 2606:4700::6812:1225
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:1325, 2606:4700::6812:1225 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 73 URLs
PASS
robots.txt present, sitemap with 73 URLs
Info::
robots.txt is present
Got: 339 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 73 entries
Info::
Sitemap index with 73 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 339 B Sitemaps referenced 1 User-agents *, facebookexternalhit Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Disallow: /author/
Disallow: /*/trackback
Disallow: /tag/
Disallow: /*/feed
Disallow: /?s=*
Disallow: /attachment/
Disallow: /*?utm_source
Disallow: /*&utm_source

# Allow Facebook scraper
User-agent: facebookexternalhit
Allow: /

Sitemap: https://xoilackv.tv/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 73 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.xoilackq.tv/
200https://xoilackq.tv/

Preferred variant: non-www

HTTP → HTTPS

301http://xoilackq.tv/ → https://xoilackq.tv/

Consistent

A+
Domain Intelligence
xoilackq.tv — via GoDaddy.com, LLC, 20 days old
PASS
xoilackq.tv — via GoDaddy.com, LLC, 20 days old
Info::
Domain registered until Apr 2, 2027 (11 months remaining)
Info::
Domain is only 20 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Apr 2, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: GoDaddy.com, LLC
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

291 days

April 2, 2027

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

20 days

Registered April 2, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:1225

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created April 2, 2026 (20 days ago)
Expires April 2, 2027 (11 months)
Last Updated April 19, 2026
Name Servers craig.ns.cloudflare.com, sandra.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:1225
Data source: rdap (0.8s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 35 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
36 ms
Total Time Total request time from DNS lookup through full response.
36 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 12 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback