Skip to content
https://ap.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 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.ap.org/
200https://ap.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ap.org/ http://www.ap.org/

HTTP version does not redirect to HTTPS

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

Certificate validity

84
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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 10 ms lookup
PASS
1 A records, 10 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.216.167.190
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1419:6200:690::279f, 2600:1419:6200:68d::279f
Info::
6 nameserver(s) configured
Got: a11-64.akam.net, a24-65.akam.net, a9-67.akam.net, a28-66.akam.net, a1-212.akam.net, a10-67.akam.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: 10 ms
Got: 10 ms
A23.216.167.190
AAAA2600:1419:6200:690::279f, 2600:1419:6200:68d::279f
CNAME
NSa11-64.akam.net, a24-65.akam.net, a9-67.akam.net, a28-66.akam.net, a1-212.akam.net, a10-67.akam.net
MX
0 ap-org.mail.protection.outlook.com
TXT
SFMC-D9K7bgxSPCMlsyGFNaZ_Meg_PpSjrs2EYrl5QeyL
syTIuJw5ovMUyTyMZ60sceqMz/AJ4BW+kVtXnmrQtjm9Lk9vr0IgCI1B6DYfnSCq45Z11p2p6lC4F4wm...
d1abxg4eb8icpv.cloudfront.net
apple-domain-verification=BDZq6aj0YvgNFsps
google-site-verification=JYxnc1rJEOm0NMoUhqLA31mq6P9CXV8wlXPkufNYoz0
facebook-domain-verification=c54fplblj1n22ojmp87m5k5iwiixee
openai-domain-verification=dv-uSG2sRkwXmO4tgr6UMxrYwkw
cisco-ci-domain-verification=42b5396fc695526347599755c2cfeae8f191e7db6c3b88be2f6...
google-site-verification=VczfNNj91BZbUadyc1h2prnjj_SJg8xNjs9-t2eySD8
_gh-associated-press-e=3c1cc50563
miro-verification=8b868ce9fe963cecac9b8a736f3c4136dc637f1b
ZOOM_verify_RDSngob7Si-WxY7IOPTnlg
MS=ms61186271
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:spf.protection.o...
adobe-idp-site-verification=2fb0968d90abb55244a76623a7e23a000c7ed65c9bb8bc5f7755...
nitro-verification-code=MzYyMjE4MzA2MzI4NDc0NDIwNg==
protonmail-verification=fb13cb099c413b21891e99e9d39ed0ce0dc0fc4c
SFMC-unhaPV4oCPGqVKZS3tFUgM0vH0DUjz9XtyvHJLNT
pardot_62432_*=90785b7ef6343e2af03f7a86d32aadb62411a36b4171d121e3f215aa3a57a127
notion-domain-verification=Vh58IvJZs3YSQ3bO8cQlWknfSXbvOAEK5dfgnK8h61R
1password-site-verification=2X5RZ3S2GVF5BKSRROK7U4S254
CAALookup not available with standard resolver
Resolved in 10 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
Redirect Chain
1 redirect(s), 621 ms total
PASS
1 redirect(s), 621 ms total
Info::
Single redirect
Got: https://ap.org → https://www.ap.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 621 ms total
Got: 621 ms

https://ap.org

9 ms · HTTP/1.1

301

https://www.ap.org/

612 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ap.org3019 msHTTP/1.1AkamaiGHost
2https://www.ap.org/200612 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:1419:6200:690::279f, 2600:1419:6200:68d::279f
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:1419:6200:690::279f, 2600:1419:6200:68d::279f Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 23 URLs
PASS
robots.txt present, sitemap with 23 URLs
Info::
robots.txt is present
Got: 517 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 23 entries
Info::
Sitemap index with 23 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 517 B Sitemaps referenced 1 User-agents PerplexityBot, ChatGPT-User, OAI-SearchBot, SemrushBot, Applebot, *, Google-Extended, ClaudeBot, Amazonbot, bingbot, GnowitNewsbot, GPTBot Blocking No — crawling allowed
User-agent: *

Sitemap: https://www.ap.org/sitemap_index.xml

User-agent: GPTBot
Crawl-delay: 600

User-agent: Google-Extended
Crawl-delay: 600

User-agent: ClaudeBot
Crawl-delay: 600

User-agent: PerplexityBot
Crawl-delay: 600

User-agent: Amazonbot
Crawl-delay: 600

User-agent: bingbot
Crawl-delay: 600

User-agent: GnowitNewsbot
Crawl-delay: 600

User-agent: ChatGPT-User
Crawl-delay: 600

User-agent: OAI-SearchBot
Crawl-delay: 600

User-agent: SemrushBot
Crawl-delay: 600

User-agent: Applebot
Crawl-delay: 600

A+
Domain Intelligence
ap.org — via Network Solutions, LLC, 35 years, 2 months old
PASS
ap.org — via Network Solutions, LLC, 35 years, 2 months old
Info::
Domain registered until Jul 24, 2028 (2 years, 3 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: Network Solutions, LLC
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

739 days

July 24, 2028

SSL certificate

84 days

Issued by DigiCert Inc

Domain age

35 years, 2 months

Registered July 25, 1991

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1419:6200:690::279f

Registrar

Network Solutions, LLC

Unlocked 6 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 Network Solutions, LLC
Created July 25, 1991 (35 years, 2 months ago)
Expires July 24, 2028 (2 years, 3 months)
Last Updated July 24, 2018
Name Servers a1-212.akam.net, a10-67.akam.net, a11-64.akam.net, a24-65.akam.net, a28-66.akam.net, a9-67.akam.net
DNSSEC Not enabled
Hosting
IP Address 2600:1419:6200:690::279f
Data source: rdap (0.6s)

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 9 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
9 ms
Total Time Total request time from DNS lookup through full response.
9 ms

Connection waterfall

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