Skip to content
https://tomorrowspayment.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.144.74: lookup 172.67.144.74: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.21.95.104: lookup 104.21.95.104: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3037::ac43:904a: lookup 2606:4700:3037::ac43:904a: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3037::6815:5f68: lookup 2606:4700:3037::6815:5f68: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

302https://www.tomorrowspayment.com/
200https://tomorrowspayment.com/

Preferred variant: non-www

HTTP → HTTPS

200http://tomorrowspayment.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 115 ms lookup
PASS
2 A records, 115 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.144.74, 104.21.95.104
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::ac43:904a, 2606:4700:3037::6815:5f68
Info::
2 nameserver(s) configured
Got: scott.ns.cloudflare.com, khloe.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
SPF record present in TXT
Info::
DNS resolution time: 115 ms
Got: 115 ms
A172.67.144.74, 104.21.95.104
AAAA2606:4700:3037::ac43:904a, 2606:4700:3037::6815:5f68
CNAME—
NSscott.ns.cloudflare.com, khloe.ns.cloudflare.com
MX—
TXT
SPF v=spf1 include:spf.brevo.com ~all
brevo-code:00b18897cff7a9928be1c3fd00c6ab0d
google-site-verification=x4kKc2ZHMKXKxwfOJoKzRG3xUEBbs2GH1IRtTxrzhQw
CAALookup not available with standard resolver
Resolved in 115 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 8ms)
PASS
Mean 24ms across 3 resolvers (spread 8ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
Info::
Quad9: 28ms
Got: 28ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://tomorrowspayment.com

https://tomorrowspayment.com

387 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tomorrowspayment.com200387 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::ac43:904a, 2606:4700:3037::6815:5f68
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::ac43:904a, 2606:4700:3037::6815:5f68 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 110 URLs
PASS
robots.txt present, sitemap with 110 URLs
Info::
robots.txt is present
Got: 131 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 110 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 131 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /hq-3278/
Disallow: /api/
Disallow: /publisher

Sitemap: https://tomorrowspayment.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 110 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
tomorrowspayment.com — via GoDaddy.com, LLC, 2 months old
PASS
tomorrowspayment.com — via GoDaddy.com, LLC, 2 months old
Info::
Domain registered until Jul 19, 2027 (10 months remaining)
Info::
Domain is only 2 months 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 Jul 19, 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

301 days

July 19, 2027

SSL certificate

86 days

Issued by Google Trust Services

Domain age

2 months

Registered July 19, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::6815:5f68

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 July 19, 2026 (2 months ago)
Expires July 19, 2027 (10 months)
Last Updated July 19, 2026
Name Servers khloe.ns.cloudflare.com, scott.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3037::6815:5f68
Data source: rdap (0.2s)

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 571 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 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.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
471 ms
Total Time Total request time from DNS lookup through full response.
572 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 390 ms Content Transfer 100 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a3e15c614bc3bc81-CDG
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a3e15c614bc3bc81-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback