Check DNS, Urls + Redirects, Certificates and Content of your Website




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
rinex.org.rw
A
196.49.7.181
No Hostname found
yes
1
0

AAAA

yes


www.rinex.org.rw
A
196.49.7.181
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 25266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.06.2019, 00:00:00 +, Signature-Inception: 21.05.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: rw
rw
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "rw" and the NextOwner "rwe". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




Zone: org.rw
org.rw
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: rinex.org.rw
rinex.org.rw
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.rinex.org.rw
www.rinex.org.rw
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.rinex.org.rw
  ns3.ricta.org.rw

rinex.org.rw
  ns1.ricta.org.rw
196.49.7.188

  ns3.ricta.org.rw
41.138.85.98
org.rw
  fork.sth.dnsnode.net / s3.stu


  ns1.ricta.org.rw


  ns3.ricta.org.rw


  ns-rw.afrinic.net / s03-ns2.jnb


  pch.ricta.org.rw / 1.ber.pch

rw
  fork.sth.dnsnode.net / s3.stu


  ns1.ricta.org.rw


  ns3.ricta.org.rw


  ns-rw.afrinic.net / s03-ns2.jnb


  pch.ricta.org.rw / 7.fra.pch


4. SOA-Entries


Domain:rw
Zone-Name:
Primary:registry.ricta.org.rw
Mail:info.ricta.org.rw
Serial:2019052905
Refresh:86400
Retry:7200
Expire:604800
TTL:3600
num Entries:5


Domain:org.rw
Zone-Name:
Primary:registry.ricta.org.rw
Mail:info.ricta.org.rw
Serial:2019052905
Refresh:86400
Retry:7200
Expire:3600000
TTL:86400
num Entries:5


Domain:rinex.org.rw
Zone-Name:
Primary:ns3.ricta.org.rw
Mail:info.ricta.org.rw
Serial:2019022502
Refresh:21600
Retry:3600
Expire:604800
TTL:86400
num Entries:2


Domain:www.rinex.org.rw
Zone-Name:
Primary:ns3.ricta.org.rw
Mail:info.ricta.org.rw
Serial:2019022502
Refresh:21600
Retry:3600
Expire:604800
TTL:86400
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://rinex.org.rw/
196.49.7.181
200

1.070
H
Date: Wed, 29 May 2019 06:12:12 GMT
Vary: Cookie,Accept-Encoding
Composed-By: SPIP 3.0.20 @ www.spip.net + spip(3.0.20),compagnon(1.4.1),dump(1.6.9),images(1.1.10),forum(1.8.40),jqueryui(1.8.21),mediabox(0.8.11),mots(2.4.13),msie_compat(1.2.0),organiseur(0.8.12),petitions(1.4.6),porte_plume(1.12.4),revisions(1.7.9),safehtml(1.4.1),sites(1.7.13),squelettes_par_rubrique(1.1.1),stats(0.4.28),svp(0.80.26),urls(1.4.26),vertebres(1.2.2),yaml(1.5.2),saisies(2.6.1),ckeditor(0.16.19),iterateurs(0.6.1),queue(0.6.6),breves(1.3.6),compresseur(1.8.11),medias(2.7.66),tw(0.8.30)
X-Spip-Cache: 86400
Last-Modified: Wed, 29 May 2019 06:12:12 GMT
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

• http://www.rinex.org.rw/
196.49.7.181
200

1.064
H
Date: Wed, 29 May 2019 06:12:13 GMT
Vary: Cookie,Accept-Encoding
Composed-By: SPIP 3.0.20 @ www.spip.net + spip(3.0.20),compagnon(1.4.1),dump(1.6.9),images(1.1.10),forum(1.8.40),jqueryui(1.8.21),mediabox(0.8.11),mots(2.4.13),msie_compat(1.2.0),organiseur(0.8.12),petitions(1.4.6),porte_plume(1.12.4),revisions(1.7.9),safehtml(1.4.1),sites(1.7.13),squelettes_par_rubrique(1.1.1),stats(0.4.28),svp(0.80.26),urls(1.4.26),vertebres(1.2.2),yaml(1.5.2),saisies(2.6.1),ckeditor(0.16.19),iterateurs(0.6.1),queue(0.6.6),breves(1.3.6),compresseur(1.8.11),medias(2.7.66),tw(0.8.30)
X-Spip-Cache: 86400
Last-Modified: Wed, 29 May 2019 06:12:13 GMT
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

• https://rinex.org.rw/
196.49.7.181
-4

0.743
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

• https://www.rinex.org.rw/
196.49.7.181
-4

0.740
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

• http://rinex.org.rw:443/
196.49.7.181
-8

0.740
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.rinex.org.rw:443/
196.49.7.181
-8

0.744
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://rinex.org.rw/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
196.49.7.181
404

0.377
A
Not Found
Visible Content:
Date: Wed, 29 May 2019 06:12:16 GMT
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.rinex.org.rw/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
196.49.7.181
404

0.376
A
Not Found
Visible Content:
Date: Wed, 29 May 2019 06:12:16 GMT
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

7. Comments


1. General Results, most used to calculate the result

Aname "rinex.org.rw" is subdomain, public suffix is "rw", top-level-domain-type is "country-code", Country is Rwanda, tld-manager is "Rwanda Internet Community and Technology Alliance (RICTA) Ltd"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 68860 milliseconds, 68.860 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.rinex.org.rw
0

no CAA entry found
1
0
rinex.org.rw
0

no CAA entry found
1
0
org.rw
0

no CAA entry found
1
0
rw
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
rinex.org.rw

ok
1
0
www.rinex.org.rw

ok
1
0
_acme-challenge.rinex.org.rw

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rinex.org.rw

Name Error - The domain name does not exist
1
0
_acme-challenge.rinex.org.rw.org.rw

Name Error - The domain name does not exist
1
0
_acme-challenge.rinex.org.rw.rinex.org.rw

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rinex.org.rw.rinex.org.rw

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rinex.org.rw.www.rinex.org.rw

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=9956587d-5f31-456b-af87-b418a575df2d


Last Result: https://check-your-website.server-daten.de/?q=rinex.org.rw - 2019-05-29 08:11:20


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=rinex.org.rw" target="_blank">Check this Site: rinex.org.rw</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro