Skip to content
https://adb.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
3 PASS 5 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.

B
Redirect Chain
1 redirect(s), 1118 ms total
REVIEW
1 redirect(s), 1118 ms total
Info::
Single redirect
Got: https://adb.org → https://www.adb.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://adb.org
Warning::
Redirect overhead: 1118 ms total
Got: 1118 ms

https://adb.org

1033 ms · HTTP/1.0

302

https://www.adb.org/

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://adb.org3021033 msHTTP/1.0BigIP
2https://www.adb.org/40385 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1067 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
259 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
521 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.07 s
Total Time Total request time from DNS lookup through full response.
1.07 s

Connection waterfall

DNS Lookup 27 ms TCP Connect 259 ms TLS Handshake 521 ms Server Processing 260 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
32 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

32
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
1 A records, 74 ms lookup
PASS
1 A records, 74 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 202.4.6.25
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a13-64.akam.net, a3-67.akam.net, a4-67.akam.net, a1-116.akam.net, a10-64.akam.net, a16-64.akam.net
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: 74 ms
Got: 74 ms
A202.4.6.25
AAAA—
CNAME—
NSa13-64.akam.net, a3-67.akam.net, a4-67.akam.net, a1-116.akam.net, a10-64.akam.net, a16-64.akam.net
MX
0 adb-org.mail.eo.outlook.com
1 adb-org.mail.protection.outlook.com
TXT
4sjounddahfsg6u7eovmt8ckun
google-site-verification=DP97KRZ8yeVyJzfSwOY1O64K2alpK2WCmVuTr01VksI
docusign=f50c082d-c9f2-4822-8a39-b6671a265ede
2igfsnom4b3l6kuj7nvuj1ct79
apple-domain-verification=UQlm8HSNEceCH287
have-i-been-pwned-verification=0279f7e35c6d94b9a605455d96795730
SPF v=spf1 include:spf.protection.outlook.com include:_spf.adb_org._d.easydmarc.pro ...
adobe-idp-site-verification=666e4259-a5a7-4ea7-bba7-afe903f48f52
apple-domain-verification=7tcYO5RrYILOZKZx
wiz-domain-verification=d9831deae9e632e0f1ceb054f878d7e81cc46818c594af1b8f9757c3...
google-site-verification=4gFcantm40ZRDC4spNkW5YskHfz16VYoK5WshCqu--k
flexera-domain-verification-eqxizvkzhjjgyxbd
rqghp3r9pf4mgic8gjrbrmmp9t
flexera-domain-verification-rvxnfbpzdxfefpzb
OTyxRsYk=e619458be5d4b883f073baa0353a7f6c
ZOOM_verify_5zmP5MWBRD-dSgd2UwrGgw
docusign=4b04b6d2-25a3-4f0d-9acc-e0cd93445d78
msfpkey=49tuypzynr2jm3mbfmhajzt86
figma-domain-verification=bf598c3aa2a7e3cad7f8522f181e94586eb020285a46599c07426b...
jamf-site-verification=Oq133nCVM8zkq041Hc8ZoA
MS=ms96552271
flexera-domain-verification-sobstlmqawrprstg
flexera-domain-verification-ltpqezzrsoicqpmy
d365mktkey=64gxgtungn208axp071fxm2yy
globalsign-domain-verification=D54770899CD725E9F658946BF2871EAF
docusign=68da2a9c-1802-420b-a722-a9a8a34283bd
docusign=2ac8b753-ac3f-440c-a650-ebcb2cc95b0c
CAALookup not available with standard resolver
Resolved in 74 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

403https://www.adb.org/
200https://adb.org/

HTTP → HTTPS

302http://adb.org/ → https://adb.org/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
adb.org — via Network Solutions, LLC, 31 years, 2 months old, hosted on ASIANDEVBANK - Asian Development Bank, US
PASS
adb.org — via Network Solutions, LLC, 31 years, 2 months old, hosted on ASIANDEVBANK - Asian Development Bank, US
Info::
Domain registered until Jul 12, 2027 (1 years, 2 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.
Info::
Hosting: ASIANDEVBANK - Asian Development Bank, US
Got: AS7306
Domain expiry

359 days

July 12, 2027

SSL certificate

32 days

Issued by Starfield Technologies, Inc.

Domain age

31 years, 2 months

Registered July 13, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ASIANDEVBANK - Asian Development Bank, US

ASN AS7306

202.4.6.25

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 13, 1995 (31 years, 2 months ago)
Expires July 12, 2027 (1 years, 2 months)
Last Updated November 19, 2022
Name Servers a1-116.akam.net, a10-64.akam.net, a13-64.akam.net, a16-64.akam.net, a3-67.akam.net, a4-67.akam.net
DNSSEC Not enabled
Hosting
IP Address 202.4.6.25
ASN AS7306 (ASIANDEVBANK - Asian Development Bank, US)
Provider ASIANDEVBANK - Asian Development Bank, US
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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback