Skip to content
https://band.us

Infrastructure

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

https://band.us

844 ms · HTTP/1.1

301

https://www.band.us/

712 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://band.us301844 msHTTP/1.1nfront
2https://www.band.us/200712 msHTTP/1.1nfront

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.band.us/
200https://band.us/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://band.us/ → https://band.us/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 33 ms TCP Connect 285 ms TLS Handshake 288 ms Server Processing 287 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
274 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 35 ms lookup
PASS
2 A records, 35 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 117.52.137.164, 117.52.137.169
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.naver.com, ns3.naver.com, ns1.naver.com
Info::
No MX records — email not configured via DNS
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: 35 ms
Got: 35 ms
A117.52.137.164, 117.52.137.169
AAAA—
CNAME—
NSns2.naver.com, ns3.naver.com, ns1.naver.com
MX—
TXT
google-site-verification=UVwfj29NdwllsnRdaQBmJIaKStoEn119D8wbaITrCDc
mailer.domain.verification=jrSPQtXYwzCqvrfL55gskbeJdbabxN
_arlfg8aiv8pi5m94qqlk9t18cktgftl
SPF v=spf1 include:navercorp.com -all
CAALookup not available with standard resolver
Resolved in 35 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+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 764 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 764 B Sitemaps referenced 3 User-agents *, Semrushbot, GPTBot, PerplexityBot, meta-externalagent, Applebot-Extended, AhrefsBot, Yeti, OAI-SearchBot, Google-Extended, ClaudeBot, Claude-SearchBot, CCBot Blocking No — crawling allowed
# Make changes for all web spiders
User-agent: *
Disallow: /n/

User-agent: AhrefsBot
User-agent: Semrushbot
Disallow: /
Allow: /favicon.ico

User-agent: Yeti
Disallow: /
Allow: /favicon.ico
Allow: /band/*/post/*
Allow: /page/*/post/*

# BOT ACCESS FOR THE PURPOSES OF AI TRAINING AND RETRIEVAL-AUGMENTED GENERATION (RAG) IS STRICTLY PROHIBITED.
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: PerplexityBot
User-agent: Google-Extended
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: meta-externalagent
User-agent: Applebot-Extended
User-agent: CCBot
Disallow: /
Allow: /favicon.ico

# sitemap.xml
Sitemap: https://www.band.us/sitemap.xml
Sitemap: https://www.band.us/sitemap/bandhome_sitemap.xml
Sitemap: https://about.band.us/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 11 entries Valid XML Yes
Sample URLs:
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback