Skip to content
https://thenounproject.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
309 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

309
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
2 A records, 28 ms lookup
PASS
2 A records, 28 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 44.207.92.34, 54.162.198.122
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-124.awsdns-15.com, ns-850.awsdns-42.net, ns-1224.awsdns-25.org, ns-1937.awsdns-50.co.uk
Info::
7 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: 28 ms
Got: 28 ms
A44.207.92.34, 54.162.198.122
AAAA—
CNAME—
NSns-124.awsdns-15.com, ns-850.awsdns-42.net, ns-1224.awsdns-25.org, ns-1937.awsdns-50.co.uk
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx5.googlemail.com
30 aspmx2.googlemail.com
30 aspmx4.googlemail.com
30 aspmx3.googlemail.com
TXT
SPF v=spf1 a mx include:mail.zendesk.com include:spf.mandrillapp.com include:servers...
MS=ms74588858
google-site-verification=WUaGa8huWTfwgQ6joPJaIGW7w-vPof0VTR43p8BU-G4
mandrill_verify.1ZG6bHkkVEiJkJpH-930uQ
google-site-verification=sEuElbj-xQb_rTKsdlbBjy_gansQraLqD5p9vHYrsa4
google-site-verification=gWfuYsux_CLtj92jtMQBVnF9__OPz5cnMSZ4rqp2hkg
CAALookup not available with standard resolver
Resolved in 28 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://thenounproject.com

https://thenounproject.com

1518 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://thenounproject.com2001518 msHTTP/1.1nginx/1.22.1
A+
Crawlability
robots.txt present, sitemap with 3905 URLs
PASS
robots.txt present, sitemap with 3905 URLs
Info::
robots.txt is present
Got: 301 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3905 entries
Info::
Sitemap index with 3905 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 301 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /undefined/
Disallow: /accounts/
Disallow: /private/

Sitemap: https://thenounproject.com/sitemap.xml
Sitemap: https://thenounproject.com/image-sitemap.xml
Sitemap: https://thenounproject.com/photo-sitemap.xml
Sitemap: https://thenounproject.com/icon-without-tags-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3905 entries Valid XML Yes
Child Sitemaps:
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.thenounproject.com/
200https://thenounproject.com/

Preferred variant: non-www

HTTP → HTTPS

301http://thenounproject.com/ → https://thenounproject.com:443/

Consistent

A
Domain Intelligence
thenounproject.com — via GoDaddy.com, LLC, 17 years, 1 months old, hosted on AWS
PASS
thenounproject.com — via GoDaddy.com, LLC, 17 years, 1 months old, hosted on AWS
Warning::
Domain expires in 41 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 2, 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

EXPIRED

June 2, 2026

SSL certificate

309 days

Issued by Amazon

Domain age

17 years, 1 months

Registered June 2, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.162.198.122

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created June 2, 2009 (17 years, 1 months ago)
Expires June 2, 2026 (1 months)
Last Updated June 3, 2025
Name Servers ns-1224.awsdns-25.org, ns-124.awsdns-15.com, ns-1937.awsdns-50.co.uk, ns-850.awsdns-42.net
DNSSEC Not enabled
Hosting
IP Address 54.162.198.122
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 558 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 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.
99 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
425 ms
Total Time Total request time from DNS lookup through full response.
558 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 97 ms TLS Handshake 99 ms Server Processing 202 ms Content Transfer 134 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback