Skip to content
https://soup.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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
Redirect Chain
1 redirect(s), 1023 ms total
REVIEW
1 redirect(s), 1023 ms total
Info::
Single redirect
Got: https://soup.io → https://www.soup.io/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1023 ms total
Got: 1023 ms

https://soup.io

502 ms · HTTP/1.1

301

https://www.soup.io/

521 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://soup.io301502 msHTTP/1.1
2https://www.soup.io/200521 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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.soup.io/
200https://soup.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://soup.io/ https://www.soup.io/

Consistent

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

Certificate validity

33
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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 188 ms lookup
PASS
1 A records, 188 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 51.81.188.11
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: ns1.weborange.com, ns2.weborange.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 188 ms
Got: 188 ms
A51.81.188.11
AAAA
CNAME
NSns1.weborange.com, ns2.weborange.com
MX
0 soup.io
TXT
google-site-verification=Dz_4Mj1mIdVKq9aa9SmkMymQrqsQoSJ2AuIbiEFwOJE
SPF v=spf1 ip4:51.81.243.148 ip4:51.81.188.11 +a +mx +ip4:51.81.183.248 +a:cloud.sud...
CAALookup not available with standard resolver
Resolved in 188 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 169 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 169 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.soup.io/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
A+
Domain Intelligence
soup.io — via GoDaddy.com, LLC, 18 years, 11 months old, hosted on OVH
PASS
soup.io — via GoDaddy.com, LLC, 18 years, 11 months old, hosted on OVH
Info::
Domain registered until Aug 7, 2026 (3 months remaining)
Info::
Registrar: GoDaddy.com, LLC
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: OVH
Got: AS16276
Domain expiry

52 days

August 7, 2026

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

18 years, 11 months

Registered August 7, 2007

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.81.188.11

Registrar

GoDaddy.com, LLC

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar GoDaddy.com, LLC
Created August 7, 2007 (18 years, 11 months ago)
Expires August 7, 2026 (3 months)
Last Updated September 21, 2025
Name Servers ns1.soup.io, ns2.soup.io
Registrant Domains By Proxy, LLC
Hosting
IP Address 51.81.188.11
ASN AS16276 (OVH, FR)
Provider OVH
Data source: whois (1.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 694 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
193 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
166 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
168 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
694 ms
Total Time Total request time from DNS lookup through full response.
694 ms

Connection waterfall

DNS Lookup 193 ms TCP Connect 166 ms TLS Handshake 168 ms Server Processing 166 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