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




Q

http sent over port 443

Checked:
11.06.2019 17:55:19


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
cirt.bf
A
192.12.116.20
/BF
No Hostname found
yes
1
0

AAAA

yes


www.cirt.bf
A
192.12.116.20
/BF
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2019, 00:00:00, Signature-Inception: 10.06.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: bf
bf
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 and the NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: cirt.bf
cirt.bf
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.cirt.bf
www.cirt.bf
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.cirt.bf
  ns1.cirt.bf / cirt-dmz-dns01

cirt.bf
  ns1.cirt.bf / cirt-dmz-dns01
192.12.116.21
/BF


  ns2.cirt.bf / ps-dnspub01
151.80.19.215
Roubaix/Nord-Pas-de-Calais/FR

bf
  censvrns0001.ird.fr


  nahouri.onatel.bf


  ns-bf.afrinic.net / s04-ns2.jnb


4. SOA-Entries


Domain:bf
Primary:nahouri.onatel.bf
Mail:hostmaster.onatel.bf
Serial:2019061001
Refresh:28800
Retry:7200
Expire:1209600
TTL:10800
num Entries:3


Domain:cirt.bf
Primary:ns1.cirt.bf
Mail:hostmaster.cirt.bf
Serial:2019060708
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:2


Domain:www.cirt.bf
Primary:ns1.cirt.bf
Mail:hostmaster.cirt.bf
Serial:2019060708
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://cirt.bf/
192.12.116.20
200

0.863
H
Date: Tue, 11 Jun 2019 15:56:14 GMT
Server: Apache
Last-Modified: Thu, 23 May 2019 12:17:57 GMT
ETag: "2cf6-5898d1284c17f"
Accept-Ranges: bytes
Content-Length: 11510
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://www.cirt.bf/
192.12.116.20
200

0.847
H
Date: Tue, 11 Jun 2019 15:56:15 GMT
Server: Apache
Last-Modified: Thu, 23 May 2019 12:17:57 GMT
ETag: "2cf6-5898d1284c17f"
Accept-Ranges: bytes
Content-Length: 11510
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• https://cirt.bf/
192.12.116.20
-4

1.444
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• https://www.cirt.bf/
192.12.116.20
-4

1.673
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• http://cirt.bf:443/
192.12.116.20
200

0.846
Q
Visible Content: Apache2 Ubuntu Default Page It works! This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. It is based on the equivalent page on Debian, from which the Ubuntu Apache packaging is derived. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html ) before continuing to operate your HTTP server. If you are a normal user of this web site and don't know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site's administrator. Configuration Overview Ubuntu's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Ubuntu tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz . Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server. The configuration layout for an Apache2 web server installation on Ubuntu systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. Configuration files in the mods-enabled/ , conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod , a2dismod , a2ensite , a2dissite , and a2enconf , a2disconf . See their respective man pages for detailed information. The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl . Calling /usr/bin/apache2 directly will not work with the default configuration. Document Roots By default, Ubuntu does not allow access through the web browser to any file apart of those located in /var/www , public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv ) you may need to whitelist your document root directory in /etc/apache2/apache2.conf . The default Ubuntu document root is /var/www/html . You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box. Reporting Problems Please use the ubuntu-bug tool to report bugs in the Apache2 package with Ubuntu. However, check existing bug reports before reporting a new bug. Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.
Date: Tue, 11 Jun 2019 15:56:21 GMT
Server: Apache
Last-Modified: Thu, 23 May 2019 12:17:57 GMT
ETag: "2cf6-5898d1284c17f"
Accept-Ranges: bytes
Content-Length: 11510
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://www.cirt.bf:443/
192.12.116.20
200

0.846
Q
Visible Content: Apache2 Ubuntu Default Page It works! This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. It is based on the equivalent page on Debian, from which the Ubuntu Apache packaging is derived. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html ) before continuing to operate your HTTP server. If you are a normal user of this web site and don't know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site's administrator. Configuration Overview Ubuntu's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Ubuntu tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz . Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server. The configuration layout for an Apache2 web server installation on Ubuntu systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. Configuration files in the mods-enabled/ , conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod , a2dismod , a2ensite , a2dissite , and a2enconf , a2disconf . See their respective man pages for detailed information. The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl . Calling /usr/bin/apache2 directly will not work with the default configuration. Document Roots By default, Ubuntu does not allow access through the web browser to any file apart of those located in /var/www , public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv ) you may need to whitelist your document root directory in /etc/apache2/apache2.conf . The default Ubuntu document root is /var/www/html . You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box. Reporting Problems Please use the ubuntu-bug tool to report bugs in the Apache2 package with Ubuntu. However, check existing bug reports before reporting a new bug. Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.
Date: Tue, 11 Jun 2019 15:56:22 GMT
Server: Apache
Last-Modified: Thu, 23 May 2019 12:17:57 GMT
ETag: "2cf6-5898d1284c17f"
Accept-Ranges: bytes
Content-Length: 11510
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://cirt.bf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
192.12.116.20
404

0.840
A
Not Found
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server.
Date: Tue, 11 Jun 2019 15:56:19 GMT
Server: Apache
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.cirt.bf/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
192.12.116.20
404

0.840
A
Not Found
Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server.
Date: Tue, 11 Jun 2019 15:56:20 GMT
Server: Apache
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

6. Comments

Aname "cirt.bf" is domain, public suffix is "bf", top-level-domain-type is "country-code", Country is Burkina Faso, tld-manager is "ARCE-AutoritÈ de RÈgulation des Communications Electroniques"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (6 urls)
http://cirt.bf/ 192.12.116.20


Url with incomplete Content-Type - header - missing charset
http://cirt.bf:443/ 192.12.116.20


Url with incomplete Content-Type - header - missing charset
http://www.cirt.bf:443/ 192.12.116.20


Url with incomplete Content-Type - header - missing charset
http://www.cirt.bf/ 192.12.116.20


Url with incomplete Content-Type - header - missing 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.
Qhttp://cirt.bf:443/ 192.12.116.20
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
Qhttp://www.cirt.bf:443/ 192.12.116.20
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
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.
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: 61846 milliseconds, 61.846 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
2
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
954680505
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-07 13:48:54
2019-09-05 13:48:54
cirt.bf - 1 entries


954503380
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-07 11:44:38
2019-09-05 11:44:38
*.cirt.bf, cirt.bf - 2 entries


303094126
leaf cert
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-02-10 00:00:00
2020-02-10 12:00:00
*.cirt.bf, cirt.bf - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
5
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1552008927
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-07 11:48:54
2019-09-05 11:48:54
cirt.bf
1 entries


1551699801
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-07 09:44:38
2019-09-05 09:44:38
*.cirt.bf, cirt.bf
2 entries


1262856959
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-06 11:04:00
2019-06-04 10:04:00
cirt.bf, www.cirt.bf
2 entries


1005823360
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-12-06 06:25:00
2019-03-06 06:25:00
cirt.bf, www.cirt.bf
2 entries


978138972
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-26 15:15:24
2019-02-24 15:15:24
cirt.bf
1 entries


803905021
leaf cert
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-02-09 23:00:00
2020-02-10 11:00:00
*.cirt.bf, cirt.bf
2 entries



10. Html-Content - Entries

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.cirt.bf
0

no CAA entry found
1
0
cirt.bf
0

no CAA entry found
1
0
bf
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
cirt.bf
v=spf1 a mx ip4:192.12.116.0/24 ~all
ok
1
0
www.cirt.bf

ok
1
0
_acme-challenge.cirt.bf
YNl0oaahCGsKo0h2obo3tkyTYuRAhFymR3KRRoP3fdo
looks good, correct length, correct characters
1
0
_acme-challenge.www.cirt.bf

Name Error - The domain name does not exist
1
0
_acme-challenge.cirt.bf.cirt.bf

Name Error - The domain name does not exist
1
0
_acme-challenge.www.cirt.bf.cirt.bf

Name Error - The domain name does not exist
1
0
_acme-challenge.www.cirt.bf.www.cirt.bf

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

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=682df27e-7074-462b-8e7f-2195ec9fbe5d


Last Result: https://check-your-website.server-daten.de/?q=cirt.bf - 2019-06-11 17:55:19


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

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