Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# As a condition of accessing this website, you agree to abide by the following
# content signals:
# (a) If a Content-Signal = yes, you may collect content for the corresponding
# use.
# (b) If a Content-Signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a Content-Signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via Content-Signal with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from your website's contents). Search does not
# include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of content for
# generative AI search answers).
# ai-train: training or fine-tuning AI models.
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# BEGIN Cloudflare Managed content
User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /
User-agent: Amazonbot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: CloudflareBrowserRenderingCrawler
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: meta-externalagent
Disallow: /
# END Cloudflare Managed Content
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations242 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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 Records4 A records, 87 ms lookupPASS
| A | 149.28.6.137, 149.28.6.1, 149.28.6.99, 149.28.6.13 |
| AAAA | — |
| CNAME | — |
| NS | ns-713.awsdns-25.net, ns-1828.awsdns-36.co.uk, ns-456.awsdns-57.com, ns-1087.awsdns-07.org |
| MX | 100 aspmx.l.google.com 150 alt2.aspmx.l.google.com 150 alt1.aspmx.l.google.com 200 aspmx3.googlemail.com 200 aspmx2.googlemail.com |
| TXT | amazonses:Q4TCQ9Fdm6Tdoe+posy9QOtTiOSlkfw+D7pb4O5xmfY= box-domain-verification=300471cc160aafedd547335f9411251eb2469d97fad02d19e13a471f... ZOOM_verify_VO8tD1liSI6wpwNeYcfHLA airtable-verification=7fde7e54eb8f6b5ce0877b9af7c7cc01 zapier-domain-verification-challenge=945132c2-70e5-4a34-83a3-a4121a61e806 google-site-verification=nur3GEsKR-6FqJ8tRBmn-C782SgXj9tQ-sU1ge8fceQ pardot640833=ed864d1395a61b3fefeb4d3b289a3f3233d03559031475fc399cc32561834eae miro-verification=2cefaa9ff3c7b041bb9304e846fad56c52f7c281 google-site-verification=4bbY1yFj4PB40UqgoCO09QPk6M-0UEFKUkGO4rKkm6U atlassian-domain-verification=DoiD3jegzLRra0ftA5eg4ojmHwkhOov5MRqQiLDY0PDQ4xMCHu... jamf-site-verification=9ZF4haoPu1h2BVrgMljwMQ apple-domain-verification=sYSprr2ksZkdafxy 00df4000001d6gyeaq UK-federation-domain-verification=33ca4df464b45dbbd3b33fcf60e0d079 google-site-verification=RYoBBDZz8MgnrcusR1mHjh5uqVz9D0BIqGIjPnWqulY SPF v=spf1 include:spf1.apsmail.org include:spf2.apsmail.org include:spf3.apsmail.or... anthropic-domain-verification-m9yxfx=ekntR1P10tkJZBZ09Lz0oCoxI openai-domain-verification=dv-i2dlDGP2xpVaxGaKe4D4ssrC |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 530 ms totalPASS
https://aps.org
393 ms · HTTP/1.1
https://www.aps.org:443/
137 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://aps.org | 301 | 393 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.aps.org:443/ | 403 | 137 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceaps.org — via NameCheap, Inc., 35 years, 1 months old, hosted on AWSPASS
40 days
August 26, 2026
242 days
Issued by Amazon
35 years, 1 months
Registered August 27, 1991
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
149.28.6.99
NameCheap, Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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