Skip to content
https://business.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.business.com/
200https://business.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 16 ms lookup
PASS
2 A records, 16 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.172.123.110, 54.83.18.24
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1278.awsdns-31.org, ns-1710.awsdns-21.co.uk, ns-346.awsdns-43.com, ns-641.awsdns-16.net
Info::
1 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: 16 ms
Got: 16 ms
A54.172.123.110, 54.83.18.24
AAAA—
CNAME—
NSns-1278.awsdns-31.org, ns-1710.awsdns-21.co.uk, ns-346.awsdns-43.com, ns-641.awsdns-16.net
MX
0 business-com.mail.protection.outlook.com
TXT
MS=ms16673938
MS=ms17913732
MS=ms26497695
MS=ms49641073
MS=ms62932901
ZOOM_verify_bR4MAXmGRCWm1QROES_Xkg
_j88l8q007ury11adv20wf7bzeq6l771
adobe-sign-verification=d30041117f4534c6ca3dfc040b75cf1
atlassian-domain-verification=d7A13knzZK2Cy8+cg0Gqx97MuBrVZRC/MsO0UI07y8ZZdPupxu...
facebook-domain-verification=6yhcypelx8hwkc1i655b5k1vq1c7yl
globalsign-domain-verification=8frsHcE2ag-0ccaaP5BTpPmUJC8ob8pdjDQchfAWzD
google-site-verification=20VLHZBJ-qHeHZ5JXl7pCFXqfbwxNqsoCM59-i47Z_I
google-site-verification=6IR6TC9L18AsrMNHPwoRijWbYXJQ0HbBkbKybx3ApEw
google-site-verification=7aDCfD-3tm9PpPp-4Uw-R6IqEr8zXGasNzSu_jmH02s
google-site-verification=AmlG6qp9CGzMsRajlKAAp61a3UP08mr9eg0vE30GYVQ
google-site-verification=KHU5tfG-okot44r8nsa7xvDo_SbRtBr8SsRpZeVREUI
google-site-verification=PU7XPAhOl6-Q0L0ImzEZF7HjJOriibob8ezpza5LEzI
google-site-verification=Ry9G4iTebQrTJ-JZbI-dv8aLgqyHHQgIWlpDH13fg-Q
google-site-verification=ekJuGLGWGcKXAMAunHbBjPE3KpwynrHolekkiU8XcH8
google-site-verification=fgizGOo9kE25vXoL-NaDwYCMYk010LDWeMPrIloplRc
j4m0t72q3lbffkgjfs33xrbzqvj7vcv3
pardot900901=36424bf4d4a5c9c5183a6682fceeb1609805c6e610dd6b1435e69c2577418611
sending_domain900901=f68ef57708371312dba67d159a562817fb9ab53a09c02967395cd86093e...
SPF v=spf1 include:spf.protection.outlook.com include:mktomail.com include:aspmx.par...
CAALookup not available with standard resolver
Resolved in 16 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), 58 ms total
PASS
1 redirect(s), 58 ms total
Info::
Single redirect
Got: https://business.com → https://www.business.com/ (301)
Info::
WWW normalization redirect

https://business.com

35 ms · HTTP/1.1

301

https://www.business.com/

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://business.com30135 msHTTP/1.1nginx
2https://www.business.com/20023 msHTTP/1.1nginx/1.29.8

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 633 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 633 B Sitemaps referenced 1 User-agents DuckAssistBot, *, anthropic-ai, GPTBot, Google-Extended, meta-externalagent, OAI-SearchBot, Applebot, BingBot, ClaudeBot, Claude-Web, FacebookBot, Amazonbot, Applebot-Extended, ChatGPT-User, ChatGPT-User/2.0, LinkedInBot, Perplexity-User, PerplexityBot Blocking No — crawling allowed
User-agent: Amazonbot
User-agent: anthropic-ai
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: BingBot
User-agent: ChatGPT-User
User-agent: ChatGPT-User/2.0
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: DuckAssistBot
User-agent: GPTBot
User-agent: Google-Extended
User-agent: LinkedInBot
User-agent: meta-externalagent
User-agent: OAI-SearchBot
User-agent: Perplexity-User
User-agent: PerplexityBot
User-agent: FacebookBot
Allow: /

User-agent: *
Disallow: /search/
Disallow: /b-newsletter/archive/
Disallow: /b-newsletter/content/
Disallow: /newsletter/ 
Sitemap: https://www.business.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
business.com — via Amazon Registrar, Inc., 28 years, 4 months old, hosted on AWS
PASS
business.com — via Amazon Registrar, Inc., 28 years, 4 months old, hosted on AWS
Info::
Domain registered until Mar 20, 2027 (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: Amazon Registrar, 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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

244 days

March 20, 2027

SSL certificate

191 days

Issued by Amazon

Domain age

28 years, 4 months

Registered April 30, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.83.18.24

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created April 30, 1998 (28 years, 4 months ago)
Expires March 20, 2027 (11 months)
Last Updated February 13, 2026
Name Servers ns-1278.awsdns-31.org, ns-1710.awsdns-21.co.uk, ns-346.awsdns-43.com, ns-641.awsdns-16.net
DNSSEC Not enabled
Hosting
IP Address 54.83.18.24
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
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 40 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
16 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
41 ms
Total Time Total request time from DNS lookup through full response.
41 ms

Connection waterfall

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