Skip to content
https://weforum.org

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 Santa Clara, United States
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
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
TLS Certificate Expiry & Recommendations
323 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

323
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, 27 ms lookup
PASS
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 34.243.178.200, 52.18.44.46
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-108.awsdns-13.com, ns-1240.awsdns-27.org, ns-1550.awsdns-01.co.uk, ns-757.awsdns-30.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: 27 ms
Got: 27 ms
A34.243.178.200, 52.18.44.46
AAAA
CNAME
NSns-108.awsdns-13.com, ns-1240.awsdns-27.org, ns-1550.awsdns-01.co.uk, ns-757.awsdns-30.net
MX
10 mxa-0029f101.gslb.pphosted.com
10 mxb-0029f101.gslb.pphosted.com
TXT
058b7f7c-f1a8-4151-bf33-7c1253b8250c
0v44yrz5mz7w4362rxvcphy6vcsz567b
21561668a4c58d5dbb50486afe176195ca06a4bd
Dynatrace-site-verification=6fb4cdfa-6d51-4c6b-ba72-32ca31fbd8e9__65807dga6ljd8g...
Dynatrace-site-verification=b6992eee-7248-43a9-97cb-ac9543820831__nf3vvnhs7i6bjl...
GIC0y5UuCphNvp5+zdLo3uM9hZCeTKMji/uUwKekuROTMgqPELHboLHV/cXBvIJXsO64CXJZim+NeI7i...
MS=ms20688131
_y0a8jocbfw3junt02mldp6b2xl3t8ek
adobe-idp-site-verification=d267447c-3316-4c5a-bd63-b478cf4d2581
apple-domain-verification=OQWui0o3waVdBNot
asv=30cf3d98cd231922c304e2ea205690bf
atlassian-domain-verification=KdxYDGkL7ybHsaieC01/GdZSKLeYss2GazxPERg1ibVNnJHIJz...
canva-site-verification=0Y_UJA27aPqQYo5C8ZlN5A
docusign=1fdc429f-b194-4a68-8321-3ed07f170b16
docusign=af7aeb30-e49c-4b7a-98d8-6b127f9bb275
google-site-verification=9UJ64WqmFileahOWizp4xsqS6ocCgUwkPfk7R5gKgFE
hcp-domain-verification=8df8c1bab58a33a3c4a18d55d756be6feecb16f1bc9ff97c4c5b56c2...
logmein-verification-code=4e3aa1a0-ba3c-408d-8415-2773f0cc7317
mixpanel-domain-verify=af7b2ab9-ba7e-4dfb-ae38-8553aaf28806
onetrust-domain-verification=4706964004d842ff8e3e998cfb9e95ee
openai-domain-verification=dv-2ERIqAfMx5ObZD0xf5vGDQQq
pardot1023261=931c4279794fd4a47b5a396730efb1ef52c243049f80e03a88d020a4a8a674be
pardot586733=df6859a87f543a1aef8e961fa54c4edf37e797ba9695931a6a5a0c41979a8a65
pp-verification=6d09c4db-136f-45b0-a876-ee9894ecb227
protonmail-verification=9a5678880a3d8a138adef690b172b83011aa72c9
sending_domain1023261=d2791adae2bac175e941031c1faea3ebf7d8d0f9bec255c60a22235e31...
sending_domain586733=f770af487ef2e5a0f69363082f6c4cc3e0def8a8c660f71eea5acd311e7...
trend-micro-v1-domain-verification.207d3dea181fe697f7b7baf200bc0723=215960e6-460...
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com +include:%{l}._spf.%{d} -all
wrike-verification=MTA5NjQyNzpiNmM1MDkzNjVjYmFlMjI0ZjQwZGVjMjdiZGIzZDYzNTNiZjU0Y...
CAALookup not available with standard resolver
Resolved in 27 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), 666 ms total
PASS
1 redirect(s), 666 ms total
Info::
Single redirect
Got: https://weforum.org → https://www.weforum.org:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 666 ms total
Got: 666 ms

https://weforum.org

593 ms · HTTP/1.1

301

https://www.weforum.org:443/

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://weforum.org301593 msHTTP/1.1awselb/2.0
2https://www.weforum.org:443/40373 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://weforum.org/ https://weforum.org:443/

Consistent

A+
Domain Intelligence
weforum.org — via Amazon Registrar, Inc., 30 years, 10 months old, hosted on AWS
PASS
weforum.org — via Amazon Registrar, Inc., 30 years, 10 months old, hosted on AWS
Info::
Domain registered until Nov 26, 2026 (7 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: AS16509
Domain expiry

165 days

November 26, 2026

SSL certificate

323 days

Issued by Amazon

Domain age

30 years, 10 months

Registered November 27, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.18.44.46

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 November 27, 1995 (30 years, 10 months ago)
Expires November 26, 2026 (7 months)
Last Updated October 27, 2025
Name Servers ns-1240.awsdns-27.org, ns-108.awsdns-13.com, ns-1550.awsdns-01.co.uk, ns-757.awsdns-30.net
DNSSEC Not enabled
Hosting
IP Address 52.18.44.46
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 7 ms TCP Connect 145 ms TLS Handshake 292 ms Server Processing 146 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