Skip to content
https://Solugenix.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
17
7 PASS 10 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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 199.60.103.102: lookup 199.60.103.102: 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 199.60.103.2: lookup 199.60.103.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.
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
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 301-redirects to HTTPS

www / non-www

200https://www.Solugenix.com/
200https://Solugenix.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://Solugenix.com/ → https://Solugenix.com/

Consistent

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

Certificate validity

53
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9f989839ab998838-SIN
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f989839ab998838-SIN
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
2 A records, 221 ms lookup
PASS
2 A records, 221 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 199.60.103.102, 199.60.103.2
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns23.domaincontrol.com, ns24.domaincontrol.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (221 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 221 ms
A199.60.103.102, 199.60.103.2
AAAA—
CNAME—
NSns23.domaincontrol.com, ns24.domaincontrol.com
MX
0 solugenix.com.1.0001.arsmtp.com
20 solugenix.com.2.0001.arsmtp.com
TXT
google-site-verification=kEz-3LC_xNQTclHLmGYUHRcWJs5I6swxf7NB1JPIXIQ
intacct-esk=4FED1A40A6B1A7E8E0539306A8C0293B
06529452666939e66930ac3f73f34fde546f89d0cf9f148bee5f31544d519cf3
A218B4B1DD
adobe-idp-site-verification=13fbfcae41f97c61d8f96bf8093c080bb12a99817a185ee978f4...
atlassian-domain-verification=8lGtVWNPNYT0C4Kl1jvak5OLCWapfr7ZF2t2ejvnOcheDjh94z...
google-site-verification=PI6hO9buqOG3qJDb-PypDI_hNPUwjteH2335k1ke_zE
K72h/fvAVFEmrUCNsg4Z/QHd5tmQ8H2O2miRmaWiYCo1OEWHP932IHFj30RGmsazw2VaZ2G00Bha9gja...
knowbe4-site-verification=b78c997d0a97801726949074167873e5
SPF v=spf1 ip4:70.163.72.210 include:spf.protection.outlook.com include:servers.mcsv...
v=verifydomain MS=ms95899892
webexdomainverification.=3b4e4b99-11e7-40a3-9c96-3f03dc16f9db
google-gws-recovery-domain-verification=57303717
CAALookup not available with standard resolver
Resolved in 221 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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 6ms across 3 resolvers (spread 8ms)
PASS
Mean 6ms across 3 resolvers (spread 8ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 6ms
Got: 6ms via 8.8.8.8:53
Info::
Quad9: 10ms
Got: 10ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 121 ms total
PASS
1 redirect(s), 121 ms total
Info::
Single redirect
Got: https://Solugenix.com → https://www.solugenix.com/ (301)
Info::
WWW normalization redirect

https://Solugenix.com

57 ms · HTTP/1.1

301

https://www.solugenix.com/

63 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Solugenix.com30157 msHTTP/1.1cloudflare
2https://www.solugenix.com/20063 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 157 URLs
PASS
robots.txt present, sitemap with 157 URLs
Info::
robots.txt is present
Got: 165 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 157 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 165 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /_hcms/preview/
Disallow: /hs/manage-preferences/
Disallow: /hs/preferences-center/
Disallow: /*?*hs_preview=*
Disallow: /*?*hsCacheBuster=*
sitemap.xml 200 OK
Type URL Set URLs 157 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
Solugenix.com — via GoDaddy.com, LLC, 21 years, 8 months old, hosted on Cloudflare
PASS
Solugenix.com — via GoDaddy.com, LLC, 21 years, 8 months old, hosted on Cloudflare
Info::
Domain registered until Dec 20, 2026 (7 months remaining)
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.
Info::
Hosting: Cloudflare
Got: AS209242
Domain expiry

219 days

December 20, 2026

SSL certificate

53 days

Issued by Google Trust Services

Domain age

21 years, 8 months

Registered December 20, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

199.60.103.102

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created December 20, 2004 (21 years, 8 months ago)
Expires December 20, 2026 (7 months)
Last Updated December 21, 2025
Name Servers ns23.domaincontrol.com, ns24.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 199.60.103.102
ASN AS209242 (CLOUDFLARESPECTRUM Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (1.1s)

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

Connection waterfall

DNS Lookup 8 ms TCP Connect 1 ms TLS Handshake 12 ms Server Processing 200 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback