Skip to content
https://www.behance.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
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
HTTP Probe Timing
Total 1049 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
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.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
2 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.05 s
Total Time Total request time from DNS lookup through full response.
1.05 s

Connection waterfall

DNS Lookup 37 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 1.01 s Content Transfer 3 ms
B
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
4 A records, 29 ms lookup
PASS
4 A records, 29 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.129.197, 151.101.1.197, 151.101.65.197, 151.101.193.197
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: behance.net
Info::
4 nameserver(s) configured
Got: ns-1714.awsdns-22.co.uk, ns-1387.awsdns-45.org, ns-478.awsdns-59.com, ns-588.awsdns-09.net
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: 29 ms
Got: 29 ms
A151.101.129.197, 151.101.1.197, 151.101.65.197, 151.101.193.197
AAAA
CNAMEbehance.net
NSns-1714.awsdns-22.co.uk, ns-1387.awsdns-45.org, ns-478.awsdns-59.com, ns-588.awsdns-09.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
SPF v=spf1 -all
google-site-verification=eaYlPjbjY48E_rtwBEPQkPGuNAOxrnqzwVIIi_QH27A
CAALookup not available with standard resolver
Resolved in 29 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.behance.net

https://www.behance.net

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.behance.net2005 msHTTP/1.1adobe
A+
Crawlability
robots.txt present, sitemap with 26 URLs
PASS
robots.txt present, sitemap with 26 URLs
Info::
robots.txt is present
Got: 1317 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 26 entries
Info::
Sitemap index with 26 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1317 B Sitemaps referenced 1 User-agents Bytespider, cohere-training-data-crawler, FacebookBot, Omgilibot, *, AI2Bot, CCbot, GPTBot, ImagesiftBot, Omgili, PanguBot, Timpibot, Webzio-Extended, anthropic-ai, Claude-Web, ClaudeBot, Kangaroo Bot, Applebot-Extended, Diffbot, Google-Extended, Meta-ExternalAgent Blocking No — crawling allowed
Sitemap: https://www.behance.net/sitemap

# Disallow AI bots
User-agent: AI2Bot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: Bytespider
User-agent: CCbot
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: cohere-training-data-crawler
User-agent: Diffbot
User-agent: FacebookBot
User-agent: Google-Extended
User-agent: GPTBot
User-agent: ImagesiftBot
User-agent: Kangaroo Bot
User-agent: Meta-ExternalAgent
User-agent: Omgili
User-agent: Omgilibot
User-agent: PanguBot
User-agent: Timpibot
User-agent: Webzio-Extended
Disallow: /

User-agent: *
Disallow: /v2/
Disallow: /v3/
Disallow: /log$
Disallow: /search/*?*assetsCategory=*
Disallow: /search/*?*assetsPriceTier=*
Disallow: /search/*?*assetsExtensionTypes=*
Disallow: /search/*?*color_hex=*
Disallow: /search/*?*country=*
Disallow: /search/*?*exif_aperture=*
Disallow: /search/*?*exif_focal_length=*
Disallow: /search/*?*exif_lens_brand=*
Disallow: /search/*?*exif_make=*
Disallow: /search/*?*exif_shutter_speed=*
Disallow: /search/*?*exif_zoom=*
Disallow: /search/*?*field=*
Disallow: /search/*?*gif=*
Disallow: /search/*?*premium=*
Disallow: /search/*?*sort=*
Disallow: /search/*?*schools=*
Disallow: /search/*?*tools=*
Disallow: /search/*?*time=*
Disallow: /search/*?*userAvailability=*
Disallow: /hire/browse
Disallow: /*/undefined

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.behance.net/
301https://behance.net/

Preferred variant: www

HTTP → HTTPS

301http://www.behance.net/ https://www.behance.net/

Consistent

A+
Domain Intelligence
behance.net — via Nom-iq Ltd. dba COM LAUDE, 20 years, 8 months old, hosted on Fastly
PASS
behance.net — via Nom-iq Ltd. dba COM LAUDE, 20 years, 8 months old, hosted on Fastly
Info::
Domain registered until Nov 6, 2026 (7 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: Nom-iq Ltd. dba COM LAUDE
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

144 days

November 6, 2026

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

20 years, 8 months

Registered November 6, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.65.197

Registrar

Nom-iq Ltd. dba COM LAUDE

Lock status unknown 2 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 Nom-iq Ltd. dba COM LAUDE
Created November 6, 2005 (20 years, 8 months ago)
Expires November 6, 2026 (7 months)
Last Updated October 7, 2025
Name Servers ns-1387.awsdns-45.org, ns-1714.awsdns-22.co.uk
DNSSEC Not enabled
Hosting
IP Address 151.101.65.197
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

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
CDN & Delivery
Fastly (MISS, MISS)
PASS
Fastly (MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-iad-kiad7000162-IAD, cache-toj-leto2350029-TOJ
Info::
CDN cache status: MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS, MISS Evidence x-served-by: cache-iad-kiad7000162-IAD, cache-toj-leto2350029-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback