Skip to content
https://ajc.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.ajc.com/
200https://ajc.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ajc.com/ → http://www.ajc.com/

HTTP version does not redirect to HTTPS

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
187 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

187
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, 19 ms lookup
PASS
2 A records, 19 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.44.140.157, 13.223.114.163
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.ajcdns.com, ns2.ajcdns.com, ns3.ajcdns.com, ns4.ajcdns.com
Info::
2 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: 19 ms
Got: 19 ms
A52.44.140.157, 13.223.114.163
AAAA—
CNAME—
NSns1.ajcdns.com, ns2.ajcdns.com, ns3.ajcdns.com, ns4.ajcdns.com
MX
10 mxb-002b3a01.gslb.pphosted.com
10 mxa-002b3a01.gslb.pphosted.com
TXT
12ft=disable
2FzwyiOOMy5QiaI9jRGBDTGE0GMWOBpKJK/gdr2wjrhFu1jLANvcPy7Llb0kK12LvfE8ShpRvZt/NRuP...
MS=ms52193138
MS=ms81967044
VCAjMuzysZhsfLEX1URfXYgfDulwb04/DHum1mJw4fAbmRYZMqym92mJFduTXmp/rJiEnVWVD8bfGf0l...
Y74cZgUkid2EykYyi5yXuM1qY7vYdip+JN0WhiSzXaz0s+27np4V8WzGNQSkIB/Yw6Jbke3I5aEKr5YV...
ZOOM_verify_sBoexKBrSliUlMCIxThowQ
_globalsign-domain-verification=CHsuX6kwSdlCasasaFTwzigaE4KR8Q8tSrpJzZsLLu
facebook-domain-verification=fz299f8km2xdrytrhswwikgueruhwd
fastly-domain-delegation-kjivzefv2okdtv1sfvvrh89l-03302018
google-site-verification=MUuoN97PCk4_v1-6KWEJkaUs5LOeextDgQX5HM5d77w
google-site-verification=N2nvh8nMbW6l-vBxz3PS7AFrkpM8U58z-a5XgP1nHPM
google-site-verification=NjsX1FVcry8vfetsoaB5KpfQ2Dmd9IdtDdnzrdSwuJ8
google-site-verification=kICuPFOcdy552vYmpxmbjmQY9-KSXA5MJv_HJ2wUB8k
pt1kif4rmunuqe07tb6o3avef0
SPF v=spf1 include:_s63487732.fdmarc.net ~all
viqf2pu71lhkaqaj6u3abmfc63
CAALookup not available with standard resolver
Resolved in 19 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), 665 ms total
PASS
1 redirect(s), 665 ms total
Info::
Single redirect
Got: https://ajc.com → https://www.ajc.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 665 ms total
Got: 665 ms

https://ajc.com

499 ms · HTTP/1.1

301

https://www.ajc.com/

166 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ajc.com301499 msHTTP/1.1nginx/1.26.3
2https://www.ajc.com/200166 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 5000 URLs
PASS
robots.txt present, sitemap with 5000 URLs
Info::
robots.txt is present
Got: 1554 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5000 entries
Info::
Sitemap index with 5000 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1554 B Sitemaps referenced 4 User-agents bingbot, Pinterestbot, GetIntent Crawler, PhantomJS, Mappy, *, Twitterbot, AhrefsbBot, SemrushBot, trendictionbot, NTENTbot, Mail.RU_Bot, Baiduspider, YandexMobileBot, WotBot, DotBot, rogerbot, AmazonAdBot, SeznamBot, Yandex, Cliqzbot, Baiduspider-video, MauiBot (crawler.feedback+wc@gmail.com), Exabot, MJ12bot, SputnikBot, Baiduspider-image, BLEXBot, SentiBot Blocking No — crawling allowed
#Block from all, these are not the droids you are looking for
User-agent: *
Disallow: /search
Disallow: /google-search
Disallow: /flatpage-

# Sitemap files
Sitemap: https://feeds.ajc.com/arc/outboundfeeds/sitemap-index/?outputType=xml
Sitemap: https://feeds.ajc.com/arc/outboundfeeds/video-sitemap/?outputType=xml
Sitemap: https://feeds.ajc.com/arc/outboundfeeds/news-sitemap/?outputType=xml
Sitemap: https://www.ajc.com/sectionmap.xml

#Twitterbot
User-agent: Twitterbot
Disallow:

#Delayed "meh" bots
User-agent: bingbot
Crawl-delay: 10
User-agent: AhrefsbBot
Crawl-delay: 15
User-agent: SemrushBot
Crawl-delay: 15
User-agent: BLEXBot
Crawl-delay: 15
User-agent: MJ12bot
Crawl-delay: 15
User-agent: AmazonAdBot
Crawl-delay: 15
User-agent: Pinterestbot
Crawl-delay: 15
User-agent: trendictionbot
Crawl-delay: 15
User-agent: NTENTbot
Crawl-delay: 15
User-agent: DotBot
Crawl-delay: 15
User-agent: rogerbot
Crawl-delay: 15
User-Agent: Exabot
Crawl-delay: 15
User-agent: GetIntent Crawler
Crawl-delay: 15

#Get off my lawn
User-agent: Yandex
Disallow: /
User-agent: YandexMobileBot
Disallow: /
User-agent: PhantomJS
Disallow: /
User-agent: SputnikBot
Disallow: /
User-agent: SeznamBot
Disallow: /
User-agent: Cliqzbot
Disallow: /  
User-agent: Mail.RU_Bot
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: Baiduspider-video
Disallow: /
User-agent: Baiduspider-image
Disallow: /
User-agent: SentiBot
Disallow: /
User-agent: MauiBot (crawler.feedback+wc@gmail.com)
Disallow: /
User-agent: Mappy
Disallow: /
User-Agent: WotBot
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 5000 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
ajc.com — via CSC Corporate Domains, Inc., 32 years, 4 months old, hosted on AWS
PASS
ajc.com — via CSC Corporate Domains, Inc., 32 years, 4 months old, hosted on AWS
Warning::
Domain expires in 39 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 31, 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: CSC Corporate Domains, 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

EXPIRED

May 31, 2026

SSL certificate

187 days

Issued by Amazon

Domain age

32 years, 4 months

Registered June 1, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.44.140.157

Registrar

CSC Corporate Domains, Inc.

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 CSC Corporate Domains, Inc.
Created June 1, 1994 (32 years, 4 months ago)
Expires May 31, 2026 (1 months)
Last Updated May 27, 2025
Name Servers ns1.ajcdns.com, ns2.ajcdns.com, ns3.ajcdns.com, ns4.ajcdns.com
DNSSEC Not enabled
Hosting
IP Address 52.44.140.157
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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 503 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
13 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
122 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
246 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
504 ms
Total Time Total request time from DNS lookup through full response.
504 ms

Connection waterfall

DNS Lookup 13 ms TCP Connect 122 ms TLS Handshake 246 ms Server Processing 123 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