Skip to content
https://reverbnation.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
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.

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
Crawlability
robots.txt present, sitemap with 30385 URLs
REVIEW
robots.txt present, sitemap with 30385 URLs
Info::
robots.txt is present
Got: 1558 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 30385 entries
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 1558 B Sitemaps referenced 1 User-agents AdsBot-Google, *, Twitterbot Blocking No — crawling allowed
User-agent: AdsBot-Google
Disallow: /audio_player/
Disallow: /controller/audio_player/
Disallow: */{link}
Disallow: */{image}

User-agent: *
Disallow: /audio_player/
Disallow: /controller/audio_player/
Disallow: /controller/facebook/
Disallow: /c/facebook/
Disallow: /controller/facebook_artist/
Disallow: /c/facebook_artist/
Disallow: /controller/subscription/
Disallow: /c/subscription/
Disallow: /subscription/
Disallow: /controller/widget/
Disallow: /widgets/trk/
Disallow: /artist/view_widget_popup
Disallow: /controller/rss/
Disallow: /main/global_search
Disallow: /main/search
Disallow: /main/search_artist
Disallow: /main/search_song
Disallow: /main/local_scene
Disallow: /fckeditor/
Disallow: /c./*
Disallow: /controller/fan_reach/*
Disallow: /c/fan_reach/*
Disallow: /fan_reach/*
Disallow: /c/fr*
Disallow: /controller/fan_reach/add_email_flash/
Disallow: /controller/fan_reach/add_email_widget/
Disallow: /store/*
Disallow: /controller/store/store_checkout/
Disallow: /store_iframe/*
Disallow: /rpk/played_song/
Disallow: /fan/feed/
Disallow: /artist/export_shows_csv/
Disallow: /page_object/page_object_status/*
Disallow: */{link}
Disallow: */{image}
Disallow: /p/*
Disallow: /system/maintenance.html
Disallow: /show/delete_saved_shows
Disallow: /venue/venue_take_ownership_from_add_show__ownership_taken
Disallow: /*/increment_lp_video_plays/*
Disallow: /rpk/artist_stats/*
Disallow: /user/account_disabled/*

User-agent: Twitterbot
Allow: /c./poni/*
Allow: /p/*

Sitemap: http://reverbnation-http-public-production.s3.amazonaws.com/sitemap.xml

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://reverbnation.com/ https://www.reverbnation.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
2 A records, 60 ms lookup
PASS
2 A records, 60 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 98.87.49.162, 54.159.102.161
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1972.awsdns-54.co.uk, ns-800.awsdns-36.net, ns-117.awsdns-14.com, ns-1132.awsdns-13.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: 60 ms
Got: 60 ms
A98.87.49.162, 54.159.102.161
AAAA
CNAME
NSns-1972.awsdns-54.co.uk, ns-800.awsdns-36.net, ns-117.awsdns-14.com, ns-1132.awsdns-13.org
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
google-site-verification=vKoPprQ3OHR48keWjnsdn5zbOuqH8cjHhwYTSv5LBD4
facebook-domain-verification=q5lr3cb0ykzlqrgp690whm7lyy9a4n
SPF v=spf1 include:_spf.reverbnation.com include:servers.mcsv.net include:transmail....
CAALookup not available with standard resolver
Resolved in 60 ms

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), 985 ms total
PASS
1 redirect(s), 985 ms total
Info::
Single redirect
Got: https://reverbnation.com → https://www.reverbnation.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 985 ms total
Got: 985 ms

https://reverbnation.com

394 ms · HTTP/1.1

301

https://www.reverbnation.com/

591 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://reverbnation.com301394 msHTTP/1.1
2https://www.reverbnation.com/200591 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A
Domain Intelligence
reverbnation.com — via GoDaddy.com, LLC, 20 years, 1 months old, hosted on AWS
PASS
reverbnation.com — via GoDaddy.com, LLC, 20 years, 1 months old, hosted on AWS
Warning::
Domain expires in 51 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 12, 2026
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: AWS
Got: AS16509
Domain expiry

Expires today

June 12, 2026

SSL certificate

191 days

Issued by Amazon

Domain age

20 years, 1 months

Registered June 12, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.159.102.161

Registrar

GoDaddy.com, LLC

Unlocked 4 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
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created June 12, 2006 (20 years, 1 months ago)
Expires June 12, 2026 (1 months)
Last Updated June 13, 2025
Name Servers ns-1132.awsdns-13.org, ns-117.awsdns-14.com, ns-1972.awsdns-54.co.uk, ns-800.awsdns-36.net
DNSSEC Not enabled
Hosting
IP Address 54.159.102.161
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 97 ms TLS Handshake 196 ms Server Processing 100 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