Skip to content
https://nvcasinos.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nvcasinos.io/
200https://nvcasinos.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nvcasinos.io/ → https://nvcasinos.io/

Consistent

B
Domain Intelligence
nvcasinos.io — via Name.com, Inc., 11 months old
REVIEW
nvcasinos.io — via Name.com, Inc., 11 months old
Critical::
Domain expires in 8 days
This domain expires on May 1, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 1, 2026
Info::
Registrar: Name.com, Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

EXPIRED

May 1, 2026

SSL certificate

88 days

Issued by Google Trust Services

Domain age

11 months

Registered May 1, 2025

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::ac43:abeb

Registrar

Name.com, Inc.

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar Name.com, Inc.
Created May 1, 2025 (11 months ago)
Expires May 1, 2026 (8 days)
Last Updated May 6, 2025
Name Servers pedro.ns.cloudflare.com, fish.ns.cloudflare.com
Registrant Domain Protection Services, Inc.
Hosting
IP Address 2606:4700:3035::ac43:abeb
Data source: whois (1.4s)

This domain expires on May 1, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

88
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
A+
DNS Records
2 A records, 53 ms lookup
PASS
2 A records, 53 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.171.235, 104.21.96.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::6815:6002, 2606:4700:3035::ac43:abeb
Info::
2 nameserver(s) configured
Got: fish.ns.cloudflare.com, pedro.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: 53 ms
Got: 53 ms
A172.67.171.235, 104.21.96.2
AAAA2606:4700:3034::6815:6002, 2606:4700:3035::ac43:abeb
CNAME—
NSfish.ns.cloudflare.com, pedro.ns.cloudflare.com
MX—
TXT
google-site-verification=qWMopVrPtK7miRwawByy5e0P4DxprBmGazcocn98Rmg
CAALookup not available with standard resolver
Resolved in 53 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://nvcasinos.io

https://nvcasinos.io

324 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nvcasinos.io200324 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::6815:6002, 2606:4700:3035::ac43:abeb
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::6815:6002, 2606:4700:3035::ac43:abeb Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 637 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 637 B Sitemaps referenced 1 User-agents peer39_crawler, ia_archiver, archive.org_bot, ia_archiver-web.archive.org, * Blocking No — crawling allowed
User-agent: peer39_crawler
Disallow: /
User-agent: ia_archiver
Disallow: /
User-agent: archive.org_bot
Disallow: /
User-agent: ia_archiver-web.archive.org
Disallow: /

User-agent: *
Allow: /*.js
Allow: /*.css
Allow: /*.jpg
Allow: /*.png
Allow: /*.svg
Allow: /*.gif
Allow: /*.jpeg
Allow: /*.webp
Allow: /build/frontend/*.js
Allow: /build/frontend/*.css
Allow: /build/frontend/*.jpg
Allow: /build/frontend/*.png
Allow: /build/frontend/*.svg
Allow: /build/frontend/*.gif
Allow: /build/frontend/*.jpeg
Allow: /build/frontend/*.webp

Disallow: /cdn-cgi/l/email-protection
Disallow: /*?
Disallow: /*&

Sitemap: https://nvcasinos.io/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 362 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
361 ms
Total Time Total request time from DNS lookup through full response.
363 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 277 ms Content Transfer 1 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0809787b0e9378-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f0809787b0e9378-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback