Skip to content
https://ivoox.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 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.

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.ivoox.com/
200https://ivoox.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ivoox.com/ https://ivoox.com/

Consistent

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

Certificate validity

308
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, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 77.73.84.18
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns-148.awsdns-18.com, ns-2041.awsdns-63.co.uk, ns-1112.awsdns-11.org
Info::
5 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: 36 ms
Got: 36 ms
A77.73.84.18
AAAA
CNAME
NSns-148.awsdns-18.com, ns-2041.awsdns-63.co.uk, ns-1112.awsdns-11.org
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
SPF v=spf1 include:_spf.google.com include:amazonses.com -all
brevo-code:e9190d281f972fd76c271ae11ff5da52
86s2x2ht9491tkzkslvzt5d8wtmh7d24
google-site-verification=HVfdB_XTz4IumRh7f4S8TlBZJf3gLvTfwYqeWgOleCw
google-site-verification=v8VMoKmYVp_eVHzFhJoAX-ndHh2f-TNRtEoR8PZ-uxc
google-site-verification=Op3G8Xf2G42sFXnFjgZT1w2CBYOANoos6nnqf0PBP5c
CAALookup not available with standard resolver
Resolved in 36 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
Redirect Chain
1 redirect(s), 394 ms total
PASS
1 redirect(s), 394 ms total
Info::
Single redirect
Got: https://ivoox.com → https://www.ivoox.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ivoox.com

https://ivoox.com

98 ms · HTTP/1.1

302

https://www.ivoox.com/

296 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ivoox.com30298 msHTTP/1.1nginx
2https://www.ivoox.com/200296 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 2492 URLs
PASS
robots.txt present, sitemap with 2492 URLs
Info::
robots.txt is present
Got: 1015 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2492 entries
Info::
Sitemap index with 2492 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1015 B Sitemaps referenced 2 User-agents *, ClaudeBot, anthropic-ai, Claude-Web Blocking No — crawling allowed
Sitemap: https://www.ivoox.com/sitemap.xml
Sitemap: https://www.ivoox.com/blog/sitemap.xml

User-agent: *
Disallow: /playerivoox_e
Disallow: /playeriVoox_e
Disallow: /player_e
Disallow: /player_n
Disallow: /player_ri
Disallow: /playerChannel_b
Disallow: /playerList_b
Disallow: /radio_er
Disallow: /editar_nk
Disallow: /editar_nb
Disallow: /escuchas_ml
Disallow: /followers_vl
Disallow: /lista-programas_ng
Disallow: /*_am_
Disallow: /*_md_
Disallow: /*_mn_
Disallow: /*_mm_
Disallow: /*_rk_
Disallow: /*_rq_
Disallow: /*_ru_
Disallow: /*_th_
Disallow: /*_v1_
Disallow: /*_wc_
Disallow: /*_5b_
Disallow: /*_a8_listener_
Disallow: /*ajx-
Disallow: /*_in.html
Disallow: /blog/cgi-bin/
Disallow: /blog/wp-admin/
Disallow: /blog/*/?*
Disallow: /blog/index.php
Disallow: /blog/xmlrpc.php
Disallow: /*_f9*.html
Disallow: */recuperar-contrasena_z2_*
Disallow: */blog/?wordfence_syncAttackData=*
Disallow: /*_e2_*

User-agent: ClaudeBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

sitemap.xml 200 OK
Type Sitemap Index URLs 2492 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ivoox.com — via Nominalia Internet SL, 18 years, 5 months old, hosted on ICMNETSYSTEMS-AS, ES
PASS
ivoox.com — via Nominalia Internet SL, 18 years, 5 months old, hosted on ICMNETSYSTEMS-AS, ES
Info::
Domain registered until Feb 6, 2034 (7 years, 10 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: Nominalia Internet SL
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: ICMNETSYSTEMS-AS, ES
Got: AS197876
Domain expiry

2761 days

February 6, 2034

SSL certificate

308 days

Issued by Sectigo Limited

Domain age

18 years, 5 months

Registered February 6, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ICMNETSYSTEMS-AS, ES

ASN AS197876

77.73.84.18

Registrar

Nominalia Internet SL

Unlocked 3 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 Nominalia Internet SL
Created February 6, 2008 (18 years, 5 months ago)
Expires February 6, 2034 (7 years, 10 months)
Last Updated February 9, 2024
Name Servers ns-1112.awsdns-11.org, ns-148.awsdns-18.com, ns-2041.awsdns-63.co.uk
DNSSEC Not enabled
Hosting
IP Address 77.73.84.18
ASN AS197876 (ICMNETSYSTEMS-AS, ES)
Provider ICMNETSYSTEMS-AS, ES
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 35 ms TCP Connect 22 ms TLS Handshake 46 ms Server Processing 31 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