Skip to content
https://angel.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 850 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 850 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# Hey human,
#
# We like robots too. Come talk robot with us.
#
# https://wellfound.com/company/wellfound/jobs
#

User-agent: *
Disallow: /_jobs/
Disallow: /*?after_sign_in=*
Disallow: /*?inFrame=*
Disallow: /*?jobId=*
Disallow: /*?jobSlug=*
Disallow: /*?preview=*
Disallow: /*?role=*
Disallow: /*&inFrame=*
Disallow: /*&jobId=*
Disallow: /*&jobSlug=*
Disallow: /*&preview=*
Disallow: /auth/
Disallow: /cdn-cgi/
Disallow: /documents/
Disallow: /embed/
Disallow: /job_listings/report_company
Disallow: /job_pairings/howitworks
Disallow: /job_profiles/embed
Disallow: /jobs/applications
Disallow: /jobs/signup
Disallow: /onboarding
Disallow: /profile/edit
Disallow: /profile/notifications
Disallow: /profile/review
Disallow: /profile/resume
Disallow: /projects/
Disallow: /re/
Disallow: /recruit/dashboard
Disallow: /social/share_modal
Disallow: /u/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

74
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f079ed05a4422a2-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f079ed05a4422a2-SJC
A+
DNS Records
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.14.64, 104.18.15.64
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: amber.ns.cloudflare.com, nick.ns.cloudflare.com
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: 7 ms
Got: 7 ms
A104.18.14.64, 104.18.15.64
AAAA
CNAME
NSamber.ns.cloudflare.com, nick.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
343512355-6055438
apple-domain-verification=G2TgrjmhmAC2wKD3
google-site-verification=0WkHfe69Yt-Mi0woXYaB7WDj8T0W2oskwMshvMV3f_A
google-site-verification=1EnbqLhI1OCelRJrfWMYH3ebueeNm8M1hcZjIO3nhok
google-site-verification=5yxdwiozCwysBvQeonI7xMuLLA1d9NpNGTKBZAbMuso
google-site-verification=AY-t0Qp-jZuBb16CaPQTT_IRoeE33sA0SZSuu2Q5fd0
google-site-verification=NOzBC9xXQ6t4dJZZxVFPDWwm9XGZ9beSjns_vT3jPSw
google-site-verification=isVyjz-F6djq-a5OgHeDmnwwJwqQCB_uG0lz_wGmKvI
google-site-verification=tTpZs3oPUOpIxnIGaFsvD1O3wEfcnvz4qAF7C5BgfKo
hcp-domain-verification=879e5126ad2ecf29a90d15f4d762240b80b2147d72d3b71ffae6f74a...
pardot853403=1d652582b22f4f6319ea39c371258f9358aef73510763b9e5d82efb7d7c62f21
segment-site-verification=paAiRwNSu7WW0kNdyq4LzL4VjD935cFU
SPF v=spf1 include:_spf.google.com -all
CAALookup not available with standard resolver
Resolved in 7 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), 78 ms total
PASS
1 redirect(s), 78 ms total
Info::
Single redirect
Got: https://angel.co → https://wellfound.com/ (301)
Info::
Cross-domain redirect detected

https://angel.co

30 ms · HTTP/1.1

301

https://wellfound.com/

48 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://angel.co30130 msHTTP/1.1cloudflare
2https://wellfound.com/20048 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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.angel.co/
200https://angel.co/

Preferred variant: non-www

HTTP → HTTPS

301http://angel.co/ https://wellfound.com/

Consistent

A+
Domain Intelligence
angel.co — via Gandi SAS, 16 years, 2 months old, hosted on Cloudflare
PASS
angel.co — via Gandi SAS, 16 years, 2 months old, hosted on Cloudflare
Info::
Domain registered until Apr 21, 2027 (1 years remaining)
Info::
Registrar: Gandi SAS
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

310 days

April 21, 2027

SSL certificate

74 days

Issued by Let's Encrypt

Domain age

16 years, 2 months

Registered April 22, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.15.64

Registrar

Gandi SAS

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Gandi SAS
Created April 22, 2010 (16 years, 2 months ago)
Expires April 21, 2027 (1 years)
Last Updated March 23, 2026
Name Servers nick.ns.cloudflare.com, amber.ns.cloudflare.com
Registrant AL Brand, Inc
Hosting
IP Address 104.18.15.64
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (0.9s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 12 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