https://www.rss.org
Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.SCORE
86
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
179 PASS 7 REVIEW 1 FIX
DMulti-Resolver DNS SpeedActionMean 154ms across 3 resolvers (spread 447ms)FIX
Multi-Resolver DNS Speed
ActionMean 154ms across 3 resolvers (spread 447ms)
Mean 154ms across 3 resolvers (spread 447ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 10ms
Got: 10ms via 8.8.8.8:53
Info::
Quad9: 450ms
Got: 450ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 447ms (min 3ms / max 450ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
DNSSEC
Unsigned (DNSSEC not deployed)
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CAA Records
No CAA records (any CA may issue certificates)
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
CReverse DNSAction0/6 IPs match cert SANREVIEW
Reverse DNS
Action0/6 IPs match cert SAN
0/6 IPs match cert SAN
Info::
PTR lookup failed for 104.26.4.28: lookup 104.26.4.28: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.26.5.28: lookup 104.26.5.28: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.69.58: lookup 172.67.69.58: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:41c: lookup 2606:4700:20::681a:41c: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::681a:51c: lookup 2606:4700:20::681a:51c: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:20::ac43:453a: lookup 2606:4700:20::ac43:453a: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
BHTTP Probe TimingTotal 941 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
HTTP Probe Timing
Total 941 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
13 msTCP Connect TCP Connect — time to establish a TCP connection to the server.
2 msTLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
17 msTime to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
514 msTotal Time Total request time from DNS lookup through full response.
941 msConnection waterfall
DNS Lookup 13 ms TCP Connect 2 ms TLS Handshake 17 ms Server Processing 482 ms Content Transfer 427 ms
BTLS Certificate Expiry & Recommendations44 days until leaf cert expires — 3 issues to addressREVIEW
TLS Certificate Expiry & Recommendations
44 days until leaf cert expires — 3 issues to address
Certificate validity
44
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
BOperational Status PageNo status page link detectedREVIEW
Operational Status Page
No status page link detected
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
BHealth Check EndpointNo conventional health endpoint foundREVIEW
Health Check Endpoint
No conventional health endpoint found
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
ADNS Records3 A records, 16 ms lookupPASS
DNS Records
3 A records, 16 ms lookup
3 A records, 16 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.4.28, 104.26.5.28, 172.67.69.58
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:41c, 2606:4700:20::681a:51c, 2606:4700:20::ac43:453a
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 16 ms
Got: 16 ms
| A | 104.26.4.28, 104.26.5.28, 172.67.69.58 |
| AAAA | 2606:4700:20::681a:41c, 2606:4700:20::681a:51c, 2606:4700:20::ac43:453a |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Resolved in 16 ms
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Why this matters
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
Subdomain Takeover
No subdomain takeover risk detected
No subdomain takeover risk detected
Info::
No CNAME record present
A+Redirect ChainNo redirects — direct accessPASS
Redirect Chain
No redirects — direct access
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.rss.org
https://www.rss.org
473 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.rss.org | 200 | 473 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (3 ms)PASS
IPv6 Readiness
IPv6 reachable (3 ms)
IPv6 reachable (3 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:41c, 2606:4700:20::681a:51c, 2606:4700:20::ac43:453a
Got: 3 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:41c, 2606:4700:20::681a:51c, 2606:4700:20::ac43:453a Connection Reachable (3 ms)
A+Crawlabilityrobots.txt present, sitemap with 500 URLsPASS
Crawlability
robots.txt present, sitemap with 500 URLs
robots.txt present, sitemap with 500 URLs
Info::
robots.txt is present
Got: 0 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 500 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
Why this matters
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
robots.txt 200 OK
Size 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml 200 OK
Type URL Set URLs 500 entries Valid XML Yes
Sample URLs:
- https://www.rss.org//Encyc/2026/9/7/world-will-be-a-better-place-if-we-emphasise-on-what-unites-us-instead-of-what-divides-.html
- https://www.rss.org//Encyc/2026/9/4/rss-marks-a-century-of-service-as-guiding-figure-dr-mohan-bhagwat-visits-london.html
- https://www.rss.org//Encyc/2026/8/31/rise-of-bharat-means-more-united-more-emancipated-humanity.html
- https://www.rss.org//Encyc/2026/8/30/united-in-oneness-and-decorated-by-diversity.html
- https://www.rss.org//Encyc/2026/8/21/rss-three-day-akhil-bharatiya-samanvay-baithak-concludes.html
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301
www / non-www
200https://www.rss.org/
301https://rss.org/
Preferred variant: www
HTTP → HTTPS
301http://www.rss.org/ → https://www.rss.org/
Consistent
A+Domain Intelligencerss.org — via GoDaddy.com, LLC, 30 years, 9 months oldPASS
Domain Intelligence
rss.org — via GoDaddy.com, LLC, 30 years, 9 months old
rss.org — via GoDaddy.com, LLC, 30 years, 9 months old
Info::
Domain registered until Jun 11, 2033 (6 years, 9 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: GoDaddy.com, 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
2441 days
June 11, 2033
SSL certificate
44 days
Issued by Google Trust Services
Domain age
30 years, 9 months
Registered June 12, 1996
DNSSEC
Not enabled
Protects against DNS spoofing
Hosting
Unknown
2606:4700:20::ac43:453a
Registrar
GoDaddy.com, LLC
Unlocked 2 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 GoDaddy.com, LLC
Created June 12, 1996 (30 years, 9 months ago)
Expires June 11, 2033 (6 years, 9 months)
Last Updated August 12, 2026
Name Servers bob.ns.cloudflare.com, tani.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::ac43:453a
Data source: rdap (0.3s)
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
ACDN & DeliveryDocument and assets on CloudflarePASS
CDN & Delivery
Document and assets on Cloudflare
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: a44ecad6bbf66eae-GRU
Info::
CDN cache status: DYNAMIC
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 16), cache BYPASS
Got: cf-ray: a44ecc376da6f1db-GRU
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a44ecad6bbf66eae-GRU
Asset hosts on a CDN
- cdnjs.cloudflare.com — Cloudflare · assets: 16 · Cache Status: BYPASS
Other asset hosts
- sangraha.net — assets: 2 · below probe threshold
- static.cloudflareinsights.com — assets: 1 · below probe threshold
- www.google.com — assets: 1 · below probe threshold
- www.googletagmanager.com — assets: 1 · below probe threshold
A+CDN Cache ObservabilityCache state: DYNAMICPASS
CDN Cache Observability
Cache state: DYNAMIC
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.