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


 

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bicsa.cu
A
200.55.178.28
Hostname: ns1.bicsa.co.cu
yes
1
0

AAAA

yes


www.bicsa.cu
A
200.55.178.26
Hostname: smtp.bicsa.cu
yes
1
0

AAAA

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






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






2 RRSIG RR to validate DNSKEY RR found






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






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






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






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: cu

cu
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: bicsa.cu

bicsa.cu
0 DS RR in the parent zone found






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 26333, Flags 256






Public Key with Algorithm 13, KeyTag 60687, Flags 257 (SEP = Secure Entry Point)






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner bicsa.cu., Algorithm: 13, 2 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 18:26:14 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 26333, Signer-Name: bicsa.cu






RRSIG-Owner bicsa.cu., Algorithm: 13, 2 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 18:26:14 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 60687, Signer-Name: bicsa.cu






Status: Good - Algorithmus 13 and DNSKEY with KeyTag 26333 used to validate the DNSKEY RRSet






Status: Good - Algorithmus 13 and DNSKEY with KeyTag 60687 used to validate the DNSKEY RRSet






Error: DNSKEY 26333 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.






Error: DNSKEY 60687 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.






Validated: RRSIG-Owner ns1.bicsa.cu., Algorithm: 13, 3 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 17:40:23 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 26333, Signer-Name: bicsa.cu






Validated: RRSIG-Owner ns2.bicsa.cu., Algorithm: 13, 3 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 17:40:23 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 26333, Signer-Name: bicsa.cu






Validated: RRSIG-Owner ns2.bicsa.cu., Algorithm: 13, 3 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 18:08:17 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 26333, Signer-Name: bicsa.cu






Validated: RRSIG-Owner ns1.bicsa.cu., Algorithm: 13, 3 Labels, original TTL: 1200 sec, Signature-expiration: 09.03.2019, 18:08:17 +, Signature-Inception: 07.02.2019, 17:26:14 +, KeyTag 26333, Signer-Name: bicsa.cu



Zone: www.bicsa.cu

www.bicsa.cu
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.bicsa.cu
  ns1.bicsa.cu

bicsa.cu
  ns1.bicsa.cu


 
200.55.178.28

  ns2.bicsa.cu


 
200.55.136.19
cu
  cu.cctld.authdns.ripe.net / ns2.nl-ams.authdns.ripe.net


  ns.ceniai.net.cu


  ns.dns.br / ns.dns.br


  ns2.ceniai.net.cu


  ns2.gip.net


  rip.psg.com

 

4. SOA-Entries


Domain:cu
Zone-Name:
Primary:ns.ceniai.net.cu
Mail:cu-tech.ceniai.inf.cu
Serial:2019020700
Refresh:3600
Retry:1800
Expire:1209600
TTL:3600
num Entries:6


Domain:bicsa.cu
Zone-Name:
Primary:ns1.bicsa.cu
Mail:nsadmin.bicsa.cu
Serial:2019012112
Refresh:43200
Retry:7200
Expire:2419200
TTL:3600
num Entries:4


Domain:www.bicsa.cu
Zone-Name:
Primary:ns1.bicsa.cu
Mail:nsadmin.bicsa.cu
Serial:2019012112
Refresh:43200
Retry:7200
Expire:2419200
TTL:3600
num Entries:1


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://www.bicsa.cu/
200.55.178.26
301
https://www.bicsa.cu/

0.393
A
Content-length: 0
Location: https://www.bicsa.cu/
Connection: close

• http://bicsa.cu/
200.55.178.28
-14


10.033
T
Timeout - The operation has timed out

• https://bicsa.cu/
200.55.178.28
-14


10.023
T
Timeout - The operation has timed out

• https://www.bicsa.cu/
200.55.178.26
200


3.027
A
Date: Thu, 07 Feb 2019 20:26:17 GMT
Last-Modified: Thu, 31 Jan 2019 18:12:33 GMT
ETag: "a7-580c4f8670640"
Accept-Ranges: bytes
Content-Length: 167
Vary: Accept-Encoding
Connection: close
Content-Type: text/html
Strict-Transport-Security: max-age=31536000;includeSubDomains;preload
Public-Key-Pins: pin-sha256="KEY1"; pin-sha256="KEY2"; max-age=15768000
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block

• http://www.bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200.55.178.26
301
https://www.bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.394
A
Visible Content:
Content-length: 0
Location: https://www.bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close

• http://bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200.55.178.28
-14


10.026
T
Timeout - The operation has timed out
Visible Content:

• https://www.bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


3.214
A
Not Found
Visible Content:
Date: Thu, 07 Feb 2019 20:26:31 GMT
Content-Length: 346
Connection: close
Content-Type: text/html; charset=iso-8859-1
Strict-Transport-Security: max-age=31536000;includeSubDomains;preload
Public-Key-Pins: pin-sha256="KEY1"; pin-sha256="KEY2"; max-age=15768000
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block

 

7. Comments


1. General Results, most used to calculate the result

Aname "bicsa.cu" is domain, public suffix is "cu", top-level-domain-type is "country-code", Country is Cuba, tld-manager is "CENIAInternet Industria y San Jose Capitolio Nacional"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: www is preferred
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 31536000 seconds = 365 days
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
https://www.bicsa.cu/ 200.55.178.26


Url with incomplete Content-Type - header - missing charset
Ahttp://www.bicsa.cu/ 200.55.178.26
301
https://www.bicsa.cu/
Correct redirect http - https with the same domain name

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

4. Content- and Performance-critical Checks

http://bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 200.55.178.28
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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
https://www.bicsa.cu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
3.214 seconds
Warning: 404 needs more then one second
ADuration: 560213 milliseconds, 560.213 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
www.bicsa.cu
200.55.178.26
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
www.bicsa.cu
200.55.178.26
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0

 

9. Certificates

1.
1.
CN=*.bicsa.cu
07.02.2019
08.05.2019
2008 days expired
*.bicsa.cu - 1 entry
1.
1.
CN=*.bicsa.cu
07.02.2019

08.05.2019
2008 days expired


*.bicsa.cu - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:031671C6AF951D79E822660D06E3CF4059EB
Thumbprint:391DEF1C68AFE5591810242F50B05786BFBBE692
SHA256 / Certificate:o1pj2NW9r3Jj74N2Mn1mP4lCJzl/4Xogi5cBxPwfaFg=
SHA256 hex / Cert (DANE * 0 1):a35a63d8d5bdaf7263ef8376327d663f894227397fe17a208b9701c4fc1f6858
SHA256 hex / PublicKey (DANE * 1 1):dc277e11cd19680487b5c0320dea7095d2679a86998b8ef4962e36283632391f
SHA256 hex / Subject Public Key Information (SPKI):dc277e11cd19680487b5c0320dea7095d2679a86998b8ef4962e36283632391f
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1329 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1329 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1132 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1132 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

 

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. 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.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.bicsa.cu
0

no CAA entry found
1
0
bicsa.cu
5
issue
letsencrypt.org
1
0

5
iodef
mailto:nsadmin@bicsa.cu
1
0
cu
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bicsa.cu
v=spf1 mx a ip4:200.55.136.16/29 include:bicsa.co.cu include:ibicsa.co.cu -all
ok
1
0
www.bicsa.cu

ok
1
0
_acme-challenge.bicsa.cu


1
0
_acme-challenge.www.bicsa.cu

Name Error - The domain name does not exist
1
0
_acme-challenge.bicsa.cu.bicsa.cu

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bicsa.cu.www.bicsa.cu

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. 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=322ae483-cd6b-4164-b2ab-c226514670a2

 

Last Result: https://check-your-website.server-daten.de/?q=bicsa.cu - 2019-02-07 20:24:10

 

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

 

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

 

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=bicsa.cu