Skip to content
http://sinvec.miastudiosx.com

Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
16
7 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
Got: document origin: Oracle Cloud
No CDN (document or assets)
Document origin Oracle Cloud

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

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.
B
Reverse DNS
1 PTR record(s) found (no cert data to match against)
REVIEW
1 PTR record(s) found (no cert data to match against)
Info::
PTR for 50.6.156.33: 50-6-156-33.unifiedlayer.com
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

www / non-www

200http://www.sinvec.miastudiosx.com/
200http://sinvec.miastudiosx.com/

Inconsistent — duplicate content risk

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, 57 ms lookup
PASS
1 A records, 57 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 50.6.156.33
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
SPF record present in TXT
Info::
DNS resolution time: 57 ms
Got: 57 ms
A50.6.156.33
AAAA—
CNAME—
NS—
MX—
TXT
SPF v=spf1 +a +mx +ip4:50.6.155.90 ~all
CAALookup not available with standard resolver
Resolved in 57 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+
Multi-Resolver DNS Speed
Mean 41ms across 3 resolvers (spread 28ms)
PASS
Mean 41ms across 3 resolvers (spread 28ms)
Info::
Quad9: 27ms
Got: 27ms via 9.9.9.9:53
Info::
Cloudflare: 43ms
Got: 43ms via 1.1.1.1:53
Info::
Google: 55ms
Got: 55ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: http://sinvec.miastudiosx.com

http://sinvec.miastudiosx.com

194 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1http://sinvec.miastudiosx.com200194 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 132 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 132 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /thank-you.html
Disallow: /tests/
Disallow: /tools/
Sitemap: https://sinvecsystems.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 18 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
miastudiosx.com — via Network Solutions, LLC, 1 years, 7 months old, hosted on NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US
PASS
miastudiosx.com — via Network Solutions, LLC, 1 years, 7 months old, hosted on NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US
Info::
Domain registered until Mar 21, 2027 (4 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: Network Solutions, 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: NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US
Got: AS19871
Domain expiry

133 days

March 21, 2027

SSL certificate

No certificate data

Domain age

1 years, 7 months

Registered March 21, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US

ASN AS19871

50.6.156.33

Registrar

Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain 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 Network Solutions, LLC
Created March 21, 2025 (1 years, 7 months ago)
Expires March 21, 2027 (4 months)
Last Updated April 1, 2026
Name Servers ns1.bluehost.com, ns2.bluehost.com
DNSSEC Not enabled
Hosting
IP Address 50.6.156.33
ASN AS19871 (NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US)
Provider NETWORK-SOLUTIONS-HOSTING - Network Solutions, LLC, US
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 58 ms TCP Connect 95 ms TLS Handshake 0 ms Server Processing 99 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