Skip to content
https://www.dribbble.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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.dribbble.com/
200https://dribbble.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.dribbble.com/ → https://dribbble.com

Consistent

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

Certificate validity

40
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, 51 ms lookup
PASS
1 A records, 51 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 3.131.150.69
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::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 51 ms
Got: 51 ms
A3.131.150.69
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 51 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 731 ms total
PASS
1 redirect(s), 731 ms total
Info::
Single redirect
Got: https://www.dribbble.com → https://dribbble.com (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 731 ms total
Got: 731 ms

https://www.dribbble.com

363 ms · HTTP/1.1

301

https://dribbble.com

368 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.dribbble.com301363 msHTTP/1.1
2https://dribbble.com200368 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 205 URLs
PASS
robots.txt present, sitemap with 205 URLs
Info::
robots.txt is present
Got: 998 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 205 entries
Info::
Sitemap index with 205 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 998 B Sitemaps referenced 1 User-agents *, PetalBot Blocking No — crawling allowed
User-agent: *
sitemap: https://dribbble.com/sitemap.xml
Disallow: /*/buckets$
Disallow: /*/click?type=*$
Disallow: /*/click$
Disallow: /*/followers$
Disallow: /*/following$
Disallow: /*/listings$
Disallow: /*/tags$
Disallow: /*/tags/*
Disallow: /account$
Disallow: /admin$
Disallow: /ads$
Disallow: /auth$
Disallow: /autocompletes/*
Disallow: /buckets/*/edit
Disallow: /blocks/*
Disallow: /colors$
Disallow: /colors/for_404.json
Disallow: /highlights/*
Disallow: /jobs/*/apply_now
Disallow: /messages$
Disallow: /messages/*
Disallow: /recommendations/*
Disallow: /sessions/new
Disallow: /shots/*/buckets
Disallow: /shots/*/comments
Disallow: /shots/*/colors.aco
Disallow: /shots/*/edit
Disallow: /shots/*/fans
Disallow: /shots/*/rebounds
Disallow: /shots/new
Disallow: /shots/day/*
Disallow: /shots/month/*
Disallow: /shots/week/*
Disallow: /shots/year/*
Disallow: /suggestions$
Disallow: /talent/matches/*
Disallow: /comments/*/likes
Disallow: /uploads/*

User-agent: PetalBot
Disallow: /search/*
sitemap.xml 200 OK
Type Sitemap Index URLs 205 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
dribbble.com — via 1API GmbH, 18 years, 3 months old
PASS
dribbble.com — via 1API GmbH, 18 years, 3 months old
Info::
Domain registered until Oct 22, 2026 (6 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: 1API GmbH
Domain expiry

102 days

October 22, 2026

SSL certificate

40 days

Issued by Let's Encrypt

Domain age

18 years, 3 months

Registered March 19, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:2035:c400:18:db55:bf00:93a1

Registrar

1API GmbH

Lock status unknown 4 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
Registrar 1API GmbH
Created March 19, 2008 (18 years, 3 months ago)
Expires October 22, 2026 (6 months)
Last Updated November 22, 2025
Name Servers ns1.dnsimple.com, ns2.dnsimple-edge.net, ns3.dnsimple.com, ns4.dnsimple-edge.org
DNSSEC Not enabled
Hosting
IP Address 2600:9000:2035:c400:18:db55:bf00:93a1
Data source: rdap (0.1s)

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

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 117 ms TLS Handshake 124 ms Server Processing 118 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