Skip to content
https://appscyborg.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 51.210.209.19 does not match any cert SAN: ns3179604.ip-51-210-209.eu
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 124ms across 3 resolvers (spread 98ms)
REVIEW
Mean 124ms across 3 resolvers (spread 98ms)
Info::
Cloudflare: 80ms
Got: 80ms via 1.1.1.1:53
Info::
Quad9: 116ms
Got: 116ms via 9.9.9.9:53
Info::
Google: 178ms
Got: 178ms via 8.8.8.8:53
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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
1 A records, 152 ms lookup
PASS
1 A records, 152 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 51.210.209.19
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns107.ovh.net, dns107.ovh.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 152 ms
Got: 152 ms
A51.210.209.19
AAAA
CNAME
NSns107.ovh.net, dns107.ovh.net
MX
0 mail.appscyborg.com
TXT
SPF v=spf1 mx -all
google-site-verification=bMORBDi8u2Y71lgnW27Y5VpTrOXAFhf_9vBt1zmm2nA
google-site-verification=xR2Mg34xiw9vdk7_Hl2zRnI2NehrqxJPWPZraC4kIDw
ahrefs-site-verification_6ad49f67c12c450b0f761dc9d746fb0e275bd6bec9ca8927e2e3c97...
CAALookup not available with standard resolver
Resolved in 152 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://appscyborg.com

https://appscyborg.com

396 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://appscyborg.com200396 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 1053 URLs
PASS
robots.txt present, sitemap with 1053 URLs
Info::
robots.txt is present
Got: 2579 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1053 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2579 B Sitemaps referenced 1 User-agents ClaudeBot, Claude-Web, anthropic-ai, Perplexity-User, Applebot-Extended, CCBot, *, ChatGPT-User, PerplexityBot, Google-Extended, cohere-ai, GPTBot, OAI-SearchBot Blocking No — crawling allowed
# Path rules are repeated in BOTH groups on purpose.
#
# Under RFC 9309 a crawler obeys exactly ONE group — the most specific one
# matching its token — and ignores every other group, including "*". So a
# named group is not an addition to the "*" rules, it REPLACES them.
#
# This file previously gave each AI crawler its own "User-agent: X /
# Allow: /" group meaning "yes, you may index us". Because those groups
# carried no Disallow lines, they granted GPTBot, OAI-SearchBot,
# ClaudeBot, anthropic-ai and PerplexityBot MORE access than an ordinary
# crawler: every path listed below was open to them and closed to
# everyone else.
#
# Anything added to one group below must be added to the other.
#
# Not every private path belongs in this file. A Disallow line is
# world-readable and therefore a published index of what someone thought
# worth hiding, while being advisory and ignored by the clients that
# matter. Paths whose protection depends on not being known are kept out
# entirely and marked unindexable with an X-Robots-Tag response header
# instead.

User-agent: *
Allow: /

# Auth and user-private pages
Disallow: /login
Disallow: /register
Disallow: /logout
Disallow: /my-account
Disallow: /change-password-account
Disallow: /delete-account
Disallow: /forgot/
Disallow: /verify/
Disallow: /expired

# Payment flow and internal endpoints (pricing is indexable — it's a marketing page)
Disallow: /payment
Disallow: /api/

# AI search, citation and corpus crawlers — explicitly permitted, on the
# same terms as everyone else. One group, many tokens: this is the form
# that keeps the path rules attached to the permission.
#
# CCBot is included deliberately. It is not only a training crawler — its
# corpus is a retrieval source for several AI search systems, so blocking
# it cost citation reach to buy a training-use refusal that a robots
# directive cannot enforce anyway. llms.txt states corpus inclusion as
# permitted, so the two agree.
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: anthropic-ai
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
Allow: /

Disallow: /login
Disallow: /register
Disallow: /logout
Disallow: /my-account
Disallow: /change-password-account
Disallow: /delete-account
Disallow: /forgot/
Disallow: /verify/
Disallow: /expired
Disallow: /payment
Disallow: /api/

# Not permitted.
User-agent: cohere-ai
Disallow: /

Sitemap: https://appscyborg.com/sitemap.xml

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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.appscyborg.com/
200https://appscyborg.com/

Preferred variant: non-www

HTTP → HTTPS

301http://appscyborg.com/ https://appscyborg.com/

Consistent

A+
Domain Intelligence
appscyborg.com — via OVH sas, 10 years, 1 months old, hosted on OVH
PASS
appscyborg.com — via OVH sas, 10 years, 1 months old, hosted on OVH
Info::
Domain registered until Aug 23, 2028 (2 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: OVH sas
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: OVH
Got: AS16276
Domain expiry

728 days

August 23, 2028

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

10 years, 1 months

Registered August 23, 2016

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.210.209.19

Registrar

OVH sas

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH sas
Created August 23, 2016 (10 years, 1 months ago)
Expires August 23, 2028 (2 years)
Last Updated February 20, 2026
Name Servers dns107.ovh.net, ns107.ovh.net
DNSSEC Enabled
Hosting
IP Address 51.210.209.19
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 155 ms TCP Connect 75 ms TLS Handshake 84 ms Server Processing 77 ms Content Transfer 150 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback