Skip to content
https://oasis-open.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.oasis-open.org/
200https://oasis-open.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://oasis-open.org/ → https://www.oasis-open.org/

Consistent

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

Certificate validity

30
days left
0d 30d 60d 90d+

Recommended actions

  • Renew certificate — 30 days remaining
  • 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, 46 ms lookup
PASS
2 A records, 46 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.49.97, 172.67.161.154
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::6815:3161, 2606:4700:3031::ac43:a19a
Info::
2 nameserver(s) configured
Got: rita.ns.cloudflare.com, karl.ns.cloudflare.com
Info::
7 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: 46 ms
Got: 46 ms
A104.21.49.97, 172.67.161.154
AAAA2606:4700:3037::6815:3161, 2606:4700:3031::ac43:a19a
CNAME—
NSrita.ns.cloudflare.com, karl.ns.cloudflare.com
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx4.googlemail.com
30 aspmx5.googlemail.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
F82AB247B9
atlassian-domain-verification=pCNaQFtma9KpQeZ5vPMJ2h1vtoEp7lsksRqZYRnJJzmdjPiOtM...
SPF v=spf1 include:_spf.google.com include:mailgun.org include:_spf.salesforce.com i...
SPF v=spf1 include:_spf.google.com include:mailgun.org include:_spf.salesforce.com i...
google-site-verification=BEHns9Do0DndXtO1yglSGJkSIKM_bzVIY-3VO1hibhQ
CAALookup not available with standard resolver
Resolved in 46 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), 958 ms total
PASS
1 redirect(s), 958 ms total
Info::
Single redirect
Got: https://oasis-open.org → https://www.oasis-open.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 958 ms total
Got: 958 ms

https://oasis-open.org

470 ms · HTTP/1.1

301

https://www.oasis-open.org/

489 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://oasis-open.org301470 msHTTP/1.1cloudflare
2https://www.oasis-open.org/200489 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::6815:3161, 2606:4700:3031::ac43:a19a
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::6815:3161, 2606:4700:3031::ac43:a19a Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 2296 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2296 B Sitemaps referenced 3 User-agents bingbot, *, Amazonbot, Bytespider, CCBot, ClaudeBot, CloudflareBrowserRenderingCrawler, Google-Extended, meta-externalagent, Applebot-Extended, GPTBot, HeadlessChrome Blocking No — crawling allowed
# 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

User-agent: *
Allow: /

# Block aggressive HeadlessChrome crawlers
User-agent: HeadlessChrome
Disallow: /wp-content/
Disallow: /wp-includes/
Disallow: /wp-admin/
Disallow: /xmlrpc.php
Disallow: /wp-login.php
Crawl-delay: 10

# Block other common aggressive crawlers
User-agent: Amazonbot
Crawl-delay: 5

User-agent: bingbot
Crawl-delay: 2

# General crawl delay for all bots
Crawl-delay: 1

Sitemap: https://www.oasis-open.org/sitemaps/kavi-sitemap-index.xml
Sitemap: https://docs.oasis-open.org/sitemap.xml
Sitemap: https://lists.oasis-open.org/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
oasis-open.org — via DNC Holdings, Inc., 28 years, 6 months old
PASS
oasis-open.org — via DNC Holdings, Inc., 28 years, 6 months old
Info::
Domain registered until Mar 3, 2027 (10 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: DNC Holdings, 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.
Domain expiry

262 days

March 3, 2027

SSL certificate

30 days

Issued by Let's Encrypt

Domain age

28 years, 6 months

Registered March 4, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3031::ac43:a19a

Registrar

DNC Holdings, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar DNC Holdings, Inc.
Created March 4, 1998 (28 years, 6 months ago)
Expires March 3, 2027 (10 months)
Last Updated April 7, 2026
Name Servers karl.ns.cloudflare.com, rita.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3031::ac43:a19a
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 451 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f087e0c09f6da7c-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f087e0c09f6da7c-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback