Infrastructure - https://afternic.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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.

B

Redirect Chain

1 redirect(s), 1343 ms total

REVIEW

1 redirect(s), 1343 ms total

Single redirect

Got: https://afternic.com → https://www.afternic.com/ (301)

WWW normalization redirect

Redirect overhead: 1343 ms total

Got: 1343 ms

https://afternic.com

992 ms · HTTP/1.1

301

https://www.afternic.com/

352 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://afternic.com	301	992 ms	HTTP/1.1
2	https://www.afternic.com/	200	352 ms	HTTP/1.1	envoy

See the visual redirect chain in the HTTP Probe tab →

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.afternic.com/

200https://afternic.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

HTTP Probe Timing

Total 1368 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

21 ms

TCP Connect

164 ms

TLS Handshake

1.02 s

Time to First Byte

1.37 s

Total Time

1.37 s

Connection waterfall

DNS Lookup 21 ms TCP Connect 164 ms TLS Handshake 1.02 s Server Processing 164 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

247 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

247

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, 32 ms lookup

PASS

1 A records, 32 ms lookup

Resolves to 1 IPv4 address(es)

Got: 216.69.141.26

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: cns1.secureserver.net, cns2.secureserver.net

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 32 ms

Got: 32 ms

A	216.69.141.26
AAAA	—
CNAME	—
NS	cns1.secureserver.net, cns2.secureserver.net
MX	10 afternic-com.mail.protection.outlook.com
TXT	cmdbcudugljn0mi3nc64ic7div 9fvt8s6ohjq0j8ic8jdk2n1h2p iciqmuec4q6ahl2aitq0fsdcp SPF v=spf1 include:secureserver.net include:spf.em.secureserver.net include:_spf.sal... dropbox-domain-verification=4d31gokpjlcx MS=ms79883879 v=spf1 mx ip4:64.95.64.0/24 ip4:63.117.214.0/24 ip4:68.178.232.0/2...
CAA	Lookup not available with standard resolver

Resolved in 32 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.

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 85 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

robots.txt does not reference a 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 85 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

# www.robotstxt.org/
# https://code.google.com/web/controlcrawlindex/

User-agent: *

sitemap.xml 200 OK

Type URL Set URLs 6 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

afternic.com — via GoDaddy.com, LLC, 27 years, 5 months old, hosted on GoDaddy

PASS

afternic.com — via GoDaddy.com, LLC, 27 years, 5 months old, hosted on GoDaddy

Domain registered until Mar 13, 2027 (11 months remaining)

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.

Registrar: GoDaddy.com, LLC

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.

Hosting: GoDaddy

Got: AS398101

Domain expiry

244 days

March 13, 2027

SSL certificate

247 days

Issued by GoDaddy.com, Inc.

Domain age

27 years, 5 months

Registered March 13, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

GoDaddy

ASN AS398101

216.69.141.26

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC

Created March 13, 1999 (27 years, 5 months ago)

Expires March 13, 2027 (11 months)

Last Updated July 29, 2025

Name Servers cns1.secureserver.net, cns2.secureserver.net

DNSSEC Not enabled

Hosting

IP Address 216.69.141.26

ASN AS398101 (GO-DADDY-COM-LLC - GoDaddy.com, LLC, US)

Provider GoDaddy

Data source: rdap (0.4s)

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