Skip to content
https://Batch-profit.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
17
10 PASS 7 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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 188.114.96.2: lookup 188.114.96.2: 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 188.114.97.2: lookup 188.114.97.2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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
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 redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.Batch-profit.com/
200https://Batch-profit.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://Batch-profit.com/ → https://batch-profit.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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, 58 ms lookup
PASS
2 A records, 58 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.2, 188.114.97.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3120::2, 2a06:98c1:3121::2
Info::
2 nameserver(s) configured
Got: naya.ns.cloudflare.com, dante.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 58 ms
Got: 58 ms
A188.114.96.2, 188.114.97.2
AAAA2a06:98c1:3120::2, 2a06:98c1:3121::2
CNAME—
NSnaya.ns.cloudflare.com, dante.ns.cloudflare.com
MX
18 route1.mx.cloudflare.net
25 route2.mx.cloudflare.net
82 route3.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
google-site-verification=7QPY57pgsFh6pjmXc0KiSuftNUpWAyMBBVUlJTtFo4g
brevo-code:b74ac904c7aa8228ac380033670c52e9
CAALookup not available with standard resolver
Resolved in 58 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 33ms across 3 resolvers (spread 4ms)
PASS
Mean 33ms across 3 resolvers (spread 4ms)
Info::
Quad9: 32ms
Got: 32ms via 9.9.9.9:53
Info::
Cloudflare: 32ms
Got: 32ms via 1.1.1.1:53
Info::
Google: 36ms
Got: 36ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 219 ms total
PASS
1 redirect(s), 219 ms total
Info::
Single redirect
Got: https://Batch-profit.com → https://www.batch-profit.com/ (308)
Info::
WWW normalization redirect

https://Batch-profit.com

108 ms · HTTP/1.1

308

https://www.batch-profit.com/

111 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Batch-profit.com308108 msHTTP/1.1cloudflare
2https://www.batch-profit.com/200111 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3120::2, 2a06:98c1:3121::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3120::2, 2a06:98c1:3121::2 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 73 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 73 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.batch-profit.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 13 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
Batch-profit.com — via Cloudflare, Inc., 2 months old
PASS
Batch-profit.com — via Cloudflare, Inc., 2 months old
Info::
Domain registered until Aug 24, 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 Aug 24, 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: Cloudflare, Inc.
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

303 days

August 24, 2027

SSL certificate

87 days

Issued by Google Trust Services

Domain age

2 months

Registered August 24, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3121::2

Registrar

Cloudflare, Inc.

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 Cloudflare, Inc.
Created August 24, 2026 (2 months ago)
Expires August 24, 2027 (10 months)
Last Updated September 5, 2026
Name Servers dante.ns.cloudflare.com, naya.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3121::2
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 175 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
176 ms
Total Time Total request time from DNS lookup through full response.
176 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 16 ms TLS Handshake 29 ms Server Processing 92 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a4fbec712fd97b51-CDG
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a4fbec712fd97b51-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