Skip to content
https://Breakingpoint.gg

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
9 PASS 7 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:20::ac43:4a71, 2606:4700:20::681a:2f1, 2606:4700:20::681a:3f1
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:20::ac43:4a71]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:20::ac43:4a71, 2606:4700:20::681a:2f1, 2606:4700:20::681a:3f1 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
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/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.2.241: lookup 104.26.2.241: 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.26.3.241: lookup 104.26.3.241: 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 172.67.74.113: lookup 172.67.74.113: 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:20::ac43:4a71: lookup 2606:4700:20::ac43:4a71: 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:20::681a:2f1: lookup 2606:4700:20::681a:2f1: 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:20::681a:3f1: lookup 2606:4700:20::681a:3f1: 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.
C
Multi-Resolver DNS Speed
Action
Mean 99ms across 3 resolvers (spread 275ms)
REVIEW
Mean 99ms across 3 resolvers (spread 275ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Quad9: 279ms
Got: 279ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 275ms (min 4ms / max 279ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

79
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
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.
A+
DNS Records
3 A records, 10 ms lookup
PASS
3 A records, 10 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.2.241, 104.26.3.241, 172.67.74.113
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:4a71, 2606:4700:20::681a:2f1, 2606:4700:20::681a:3f1
Info::
2 nameserver(s) configured
Got: ivy.ns.cloudflare.com, ram.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 10 ms
Got: 10 ms
A104.26.2.241, 104.26.3.241, 172.67.74.113
AAAA2606:4700:20::ac43:4a71, 2606:4700:20::681a:2f1, 2606:4700:20::681a:3f1
CNAME—
NSivy.ns.cloudflare.com, ram.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
google-site-verification=PQegG-ZBXAjHSsTXmQsGfoJ5CFRqhW-dwoatzxgQDQM
SPF v=spf1 include:_spf.google.com include:amazonses.com ~all
CAALookup not available with standard resolver
Resolved in 10 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://Breakingpoint.gg

https://Breakingpoint.gg

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Breakingpoint.gg20054 msHTTP/1.1cloudflare
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.Breakingpoint.gg/
200https://Breakingpoint.gg/

Preferred variant: non-www

HTTP → HTTPS

301http://Breakingpoint.gg/ → https://origin.breakingpoint.gg:443/

Consistent

A+
Domain Intelligence
Breakingpoint.gg — via NameCheap, Inc, 5 years, 8 months old, hosted on Cloudflare
PASS
Breakingpoint.gg — via NameCheap, Inc, 5 years, 8 months old, hosted on Cloudflare
Info::
Registrar: NameCheap, 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

Unknown

SSL certificate

79 days

Issued by Google Trust Services

Domain age

5 years, 8 months

Registered September 21, 2020

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.26.2.241

Registrar

NameCheap, Inc

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc
Created September 21, 2020 (5 years, 8 months ago)
Name Servers ivy.ns.cloudflare.com, ram.ns.cloudflare.com
Hosting
IP Address 104.26.2.241
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (1.0s)

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 64 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
10 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
61 ms
Total Time Total request time from DNS lookup through full response.
64 ms

Connection waterfall

DNS Lookup 10 ms TCP Connect 3 ms TLS Handshake 11 ms Server Processing 38 ms Content Transfer 3 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f9afd1b0b31174e-SJC
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f9afd1b0b31174e-SJC
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=10, cf-cache-status=HIT
A+
Health Check Endpoint
Health endpoint at https://Breakingpoint.gg/api/health (HTTP 200)
PASS
Health endpoint at https://Breakingpoint.gg/api/health (HTTP 200)
Info::
Public health endpoint at https://Breakingpoint.gg/api/health
Got: https://Breakingpoint.gg/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback