Skip to content
https://hrefs.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
17
9 PASS 8 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.15.210: lookup 104.26.15.210: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.14.210: lookup 104.26.14.210: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.74.138: lookup 172.67.74.138: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::ac43:4a8a: lookup 2606:4700:20::ac43:4a8a: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:ed2: lookup 2606:4700:20::681a:ed2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:fd2: lookup 2606:4700:20::681a:fd2: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
33 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

33
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
Document and assets on Cloudflare
REVIEW
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a4c6da271e7c0f83-EWR
Info::
Assets on Cloudflare: ahrefs.com (assets: 108), cache HIT
Got: cf-ray: a4c6dc471f1a7327-EWR
Info::
Assets on Cloudflare: static.ahrefs.com (assets: 15), cache HIT
Got: cf-ray: a4c6dc471bae0fab-EWR
Info::
Assets on Cloudflare: cdn-cookieyes.com (assets: 4), cache HIT
Got: cf-ray: a4c6dc471bbf7cf3-EWR
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a4c6da271e7c0f83-EWR

Asset hosts on a CDN

  • ahrefs.com — Cloudflare · assets: 108 · Cache Status: HIT
  • static.ahrefs.com — Cloudflare · assets: 15 · Cache Status: HIT
  • cdn-cookieyes.com — Cloudflare · assets: 4 · Cache Status: HIT

Other asset hosts

  • analytics.twitter.com — assets: 2 · below probe threshold
  • connect.facebook.net — assets: 2 · below probe threshold
  • t.co — assets: 2 · below probe threshold
  • googleads.g.doubleclick.net — assets: 1 · below probe threshold
  • snap.licdn.com — assets: 1 · below probe threshold
  • static.ads-twitter.com — assets: 1 · below probe threshold
  • static.cloudflareinsights.com — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
  • www.redditstatic.com — assets: 1 · below probe threshold
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
3 A records, 15 ms lookup
PASS
3 A records, 15 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.15.210, 104.26.14.210, 172.67.74.138
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:4a8a, 2606:4700:20::681a:ed2, 2606:4700:20::681a:fd2
Info::
2 nameserver(s) configured
Got: adam.ns.cloudflare.com, yolanda.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
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: 15 ms
Got: 15 ms
A104.26.15.210, 104.26.14.210, 172.67.74.138
AAAA2606:4700:20::ac43:4a8a, 2606:4700:20::681a:ed2, 2606:4700:20::681a:fd2
CNAME—
NSadam.ns.cloudflare.com, yolanda.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 15 ms

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 8ms across 3 resolvers (spread 12ms)
PASS
Mean 8ms across 3 resolvers (spread 12ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Quad9: 7ms
Got: 7ms via 9.9.9.9:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 81 ms total
PASS
1 redirect(s), 81 ms total
Info::
Single redirect
Got: https://hrefs.com → https://ahrefs.com/ (301)
Info::
Cross-domain redirect detected

https://hrefs.com

39 ms · HTTP/1.1

301

https://ahrefs.com/

42 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hrefs.com30139 msHTTP/1.1cloudflare
2https://ahrefs.com/20042 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (3 ms)
PASS
IPv6 reachable (3 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:4a8a, 2606:4700:20::681a:ed2, 2606:4700:20::681a:fd2
Got: 3 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:4a8a, 2606:4700:20::681a:ed2, 2606:4700:20::681a:fd2 Connection Reachable (3 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 908 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 908 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /article
Disallow: /site-explorer/ajax/
Allow: /site-explorer/$
Disallow: /site-explorer/*
Allow: /link-intersect/$
Disallow: /link-intersect/*
Disallow: /v4*
Disallow: /blog/*?s=*
Disallow: /blog/*?archive*
Disallow: /seo/for/*?*draft
Disallow: /academy/*?*draft
Disallow: /seo-toolbar/welcome
Disallow: /seo-toolbar/uninstall
Disallow: /*/seo-toolbar/welcome
Disallow: /*/seo-toolbar/uninstall
Disallow: /*?input
Disallow: /draft/*
Disallow: /academy/draft/*
Allow: /agencies/*?services[]=*
Allow: /agencies/*&services[]=*
Disallow: /agencies/*?*languages[]=*
Disallow: /agencies/*&*languages[]=*
Disallow: /agencies/*?*industries[]=*
Disallow: /agencies/*&*industries[]=*
Disallow: /agencies/*?*budget=*
Disallow: /agencies/*&*budget=*
Disallow: /agencies/*?*businessSize=*
Disallow: /agencies/*&*businessSize=*
Disallow: /cdn-cgi/
Disallow: /writing-tools/experimental-tools.json
sitemap.xml 200 OK
Type Sitemap Index URLs 7 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::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

403https://www.hrefs.com/
200https://hrefs.com/

HTTP → HTTPS

301http://hrefs.com/ → https://ahrefs.com/

Consistent

A+
Domain Intelligence
hrefs.com — via Name.com, Inc., 8 years, 2 months old
PASS
hrefs.com — via Name.com, Inc., 8 years, 2 months old
Info::
Domain registered until Sep 28, 2029 (2 years, 11 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: Name.com, Inc.
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.
Domain expiry

1076 days

September 28, 2029

SSL certificate

33 days

Issued by Google Trust Services

Domain age

8 years, 2 months

Registered September 28, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:ed2

Registrar

Name.com, Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Name.com, Inc.
Created September 28, 2018 (8 years, 2 months ago)
Expires September 28, 2029 (2 years, 11 months)
Last Updated June 9, 2022
Name Servers adam.ns.cloudflare.com, yolanda.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:ed2
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

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 39 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 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.
40 ms
Total Time Total request time from DNS lookup through full response.
40 ms

Connection waterfall

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