Skip to content
https://realmoneygaming.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3035::6815:1c13, 2606:4700:3035::ac43:aa2c
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3035::6815:1c13]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:3035::6815:1c13, 2606:4700:3035::ac43:aa2c Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
HTTP Probe Timing
Total 1081 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
16 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 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.
1.08 s
Total Time Total request time from DNS lookup through full response.
1.08 s

Connection waterfall

DNS Lookup 16 ms TCP Connect 4 ms TLS Handshake 10 ms Server Processing 1.05 s Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
35 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

35
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, 111 ms lookup
PASS
2 A records, 111 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.170.44, 104.21.28.19
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::6815:1c13, 2606:4700:3035::ac43:aa2c
Info::
2 nameserver(s) configured
Got: owen.ns.cloudflare.com, ulla.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: 111 ms
Got: 111 ms
A172.67.170.44, 104.21.28.19
AAAA2606:4700:3035::6815:1c13, 2606:4700:3035::ac43:aa2c
CNAME—
NSowen.ns.cloudflare.com, ulla.ns.cloudflare.com
MX—
TXT
google-site-verification=oYpQqSleICTfcDcd_0OZYBNQetQsHcqCxrkb7KvXCOo
CAALookup not available with standard resolver
Resolved in 111 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://realmoneygaming.ca

https://realmoneygaming.ca

758 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://realmoneygaming.ca200758 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 541 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 541 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /cgi-bin

Disallow: /wp-admin

Disallow: /wp-includes

Disallow: /wp-content/plugins

Disallow: /wp-content/cache

Disallow: /wp-content/themes

Disallow: /wp-trackback

Disallow: /wp-feed

Disallow: /wp-comments

Disallow: */trackback

Disallow: */feed

Disallow: */comments

Disallow: /goto/*

Disallow: /out/*

Disallow: */page/*

Disallow: /*utm*

Disallow: /?attachment_id*

Disallow: */?*



Disallow: /content_manager

Host:       https://realmoneygaming.ca
Sitemap:    https://realmoneygaming.ca/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 7 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.realmoneygaming.ca/
200https://realmoneygaming.ca/

Preferred variant: non-www

HTTP → HTTPS

301http://realmoneygaming.ca/ → https://realmoneygaming.ca/

Consistent

A
Domain Intelligence
realmoneygaming.ca — via Go Get Canada Domain Registrar Ltd., 4 years, 11 months old, hosted on Cloudflare
PASS
realmoneygaming.ca — via Go Get Canada Domain Registrar Ltd., 4 years, 11 months old, hosted on Cloudflare
Warning::
Domain expires in 54 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 16, 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: Go Get Canada Domain Registrar Ltd.
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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

EXPIRED

June 16, 2026

SSL certificate

35 days

Issued by Google Trust Services

Domain age

4 years, 11 months

Registered June 16, 2021

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.67.170.44

Registrar

Go Get Canada Domain Registrar Ltd.

Unlocked 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
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Go Get Canada Domain Registrar Ltd.
Created June 16, 2021 (4 years, 11 months ago)
Expires June 16, 2026 (1 months)
Last Updated June 3, 2025
Name Servers owen.ns.cloudflare.com, ulla.ns.cloudflare.com
DNSSEC Not enabled
Registrant Harrison Gardner
Hosting
IP Address 172.67.170.44
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

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

Source: ICANN renewal policy

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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f07bd7418e1af1b-SJC
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f07bd7418e1af1b-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback