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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




V

Connect failure - perhaps firewall

Checked:
14.02.2020 09:53:28


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
xlauncher.ru
A
41.216.191.154
Moscow/Russia (RU) - LLC Digital Network
No Hostname found
yes
1
0

AAAA

yes


www.xlauncher.ru

Name Error
yes
1
0


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 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.03.2020, 00:00:00, Signature-Inception: 10.02.2020, 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: ru
ru
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.02.2020, 05:00:00, Signature-Inception: 14.02.2020, 04:00:00, KeyTag 33853, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33853 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 49959, Flags 256



Public Key with Algorithm 8, KeyTag 52263, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 02.03.2020, 00:00:00, Signature-Inception: 11.02.2020, 00:00:00, KeyTag 55747, Signer-Name: ru



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 55747, DigestType 2 and Digest "d4BsRdykFfvY/e6gpDbuaP5qpbPCO02J4Du+8zT6DLY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: xlauncher.ru
xlauncher.ru
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: www.xlauncher.ru
www.xlauncher.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.xlauncher.ru
  ns1.reg.ru

xlauncher.ru
  ns1.reg.ru / ns6.reg.ru
176.99.13.11
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.13
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.15
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.17
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.11
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.13
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.15
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.17
Moscow/Russia (RU) - Domain names registrar REG.RU


 
2a00:f940:4::47
Cheryomushki District/Moscow/Russia (RU) - Reg.Ru SRS Infrastructure


  ns2.reg.ru / ns6.reg.ru
176.99.13.12
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.14
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.16
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.18
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.12
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.14
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.16
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.18
Moscow/Russia (RU) - Domain names registrar REG.RU


 
2a00:f940:5::190
Cheryomushki District/Moscow/Russia (RU) - Reg.Ru SRS Infrastructure

ru
  a.dns.ripn.net / tau.ripn.net


  b.dns.ripn.net


  d.dns.ripn.net / gamma2-nsk.ripn.net


  e.dns.ripn.net


  f.dns.ripn.net / tau-sin.ripn.net


4. SOA-Entries


Domain:ru
Primary:a.dns.ripn.net
Mail:hostmaster.ripn.net
Serial:4041502
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:xlauncher.ru
Primary:ns1.reg.ru
Mail:hostmaster.ns1.reg.ru
Serial:1581658301
Refresh:14400
Retry:3600
Expire:604800
TTL:10800
num Entries:18


5. Screenshots (Beta)

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

6. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://xlauncher.ru/
41.216.191.154 GZip used - 547 / 1047 - 47.76 %
200

Html is minified: 213.24 %
0.127
H
Server: nginx
Date: Fri, 14 Feb 2020 08:54:25 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Last-Modified: Fri, 14 Feb 2020 05:20:27 GMT
ETag: W/"dfb46-417-59e825d04fadb"
Content-Encoding: gzip

• https://xlauncher.ru/
41.216.191.154
-2

1.204
V
ConnectFailure - Unable to connect to the remote server

• http://xlauncher.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
41.216.191.154
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
0.123
A
Visible Content: check-your-website-dot-server-daten-dot-de.ylhruX1vwKd3dHLHdRiH8PEcjpi4Zl0_bfa-vOhmQ3U
Server: nginx
Date: Fri, 14 Feb 2020 08:54:26 GMT
Content-Type: text/plain
Content-Length: 86
Connection: close

7. Comments

Aname "xlauncher.ru" is domain, public suffix is "ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Agood - only one version with Http-Status 200
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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)
http://xlauncher.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 41.216.191.154


Url with incomplete Content-Type - header - missing charset
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.
Nxlauncher.ru:465


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nxlauncher.ru:993


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nxlauncher.ru:995


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nxlauncher.ru:8083


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N41.216.191.154:465


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N41.216.191.154:993


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N41.216.191.154:995


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
N41.216.191.154:8083


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Vhttps://xlauncher.ru/ 41.216.191.154
-2

connect failure - perhaps firewall
AGood: Nameserver supports TCP connections: 18 good Nameserver
AGood: Nameserver supports Echo Capitalization: 18 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 18 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 18 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.reg.ru: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.reg.ru,ns2.reg.ru
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.
Ahttp://xlauncher.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 41.216.191.154
200

Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 131663 milliseconds, 131.663 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
xlauncher.ru
xlauncher.ru
465
Certificate/chain invalid and wrong name






error checking OCSP stapling
ok
xlauncher.ru
xlauncher.ru
465
Certificate/chain invalid and wrong name







error checking OCSP stapling
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
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

xlauncher.ru
xlauncher.ru
993
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
xlauncher.ru
xlauncher.ru
993
Certificate/chain invalid and wrong name
Tls12

DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
  Tls.1.2
Tls.1.1
Tls.1.0
Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

xlauncher.ru
xlauncher.ru
995
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
xlauncher.ru
xlauncher.ru
995
Certificate/chain invalid and wrong name
Tls12

DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
  Tls.1.2
Tls.1.1
Tls.1.0
Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

xlauncher.ru
xlauncher.ru
8083
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
xlauncher.ru
xlauncher.ru
8083
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN  Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

41.216.191.154
41.216.191.154
465
Certificate/chain invalid and wrong name






error checking OCSP stapling
ok
41.216.191.154
41.216.191.154
465
Certificate/chain invalid and wrong name







error checking OCSP stapling
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
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

41.216.191.154
41.216.191.154
993
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
41.216.191.154
41.216.191.154
993
Certificate/chain invalid and wrong name
Tls12

DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
  Tls.1.2
Tls.1.1
Tls.1.0
Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

41.216.191.154
41.216.191.154
995
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
41.216.191.154
41.216.191.154
995
Certificate/chain invalid and wrong name
Tls12

DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
  Tls.1.2
Tls.1.1
Tls.1.0
Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru

41.216.191.154
41.216.191.154
8083
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
41.216.191.154
41.216.191.154
8083
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
error checking OCSP stapling
ok
no http/2 via ALPN  Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate
1CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, C=US, emailAddress=bych@bk.ru


9. Certificates

1.
1.
E=bych@bk.ru, CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, S=California, C=US
14.02.2020
13.02.2021
expires in 318 days

1.
1.
E=bych@bk.ru, CN=localhost.example.com, OU=IT, O=Vesta Control Panel, L=San Francisco, S=California, C=US
14.02.2020

13.02.2021
expires in 318 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008536EC0DEFCF6612
Thumbprint:016A16B1852EB76D718342DF158ECF8AA023DFE2
SHA256 / Certificate:1JNjHQAy0Dvic0kaWnmQNHFVJ9IOYI96L375rl/ttp4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):797bf3b95a8d893c0d961a07aeb00b1cd34d609503efb36bccd5f6287fdea2bd
SHA256 hex / Subject Public Key Information (SPKI):3fbf56c79aecdab3d45f0eeb99f629f937d8517d8052cc6239e1a775ff6ff1e4
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1387276006
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-25 16:04:32
2020-04-24 16:04:32
www.xlauncher.ru, xlauncher.ru - 2 entries


1387237037
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-25 15:42:03
2020-04-24 15:42:03
www.xlauncher.ru, xlauncher.ru - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow (Update 2020-01-11: Should now work again - code updated. Old message: currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
2
10

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2388830204
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-25 15:04:32
2020-04-24 14:04:32
www.xlauncher.ru, xlauncher.ru
2 entries


2396596955
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-25 14:42:03
2020-04-24 13:42:03
www.xlauncher.ru, xlauncher.ru
2 entries


2104671823
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-12 22:55:33
2020-02-10 22:55:33
www.xlauncher.ru, xlauncher.ru
2 entries


1844008507
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-22 02:50:13
2019-11-20 03:50:13
www.xlauncher.ru, xlauncher.ru
2 entries


1366600610
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-06 02:10:08
2019-07-05 02:10:08
www.xlauncher.ru, xlauncher.ru
2 entries


1174187786
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-02-04 03:03:36
2019-05-05 02:03:36
www.xlauncher.ru, xlauncher.ru
2 entries


1002887241
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-12-05 03:29:13
2019-03-05 03:29:13
www.xlauncher.ru, xlauncher.ru
2 entries


820044091
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-10-05 01:41:33
2019-01-03 02:41:33
www.xlauncher.ru, xlauncher.ru
2 entries


749831929
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-08-05 01:49:50
2018-11-03 02:49:50
www.xlauncher.ru, xlauncher.ru
2 entries


508597617
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-06-05 11:25:27
2018-09-03 11:25:27
www.xlauncher.ru, xlauncher.ru
2 entries



11. Html-Content - Entries

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


12. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
xlauncher.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


13. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
xlauncher.ru

ok
1
0
_acme-challenge.xlauncher.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.xlauncher.ru.xlauncher.ru

Name Error - The domain name does not exist
1
0


14. Portchecks

Domain or IPPortDescriptionResultAnswer
xlauncher.ru
21
FTP
open
220 (vsFTPd 2.2.2)

xlauncher.ru
21
FTP
open
220 (vsFTPd 2.2.2)

xlauncher.ru
22
SSH
open
SSH-2.0-OpenSSH_5.3

xlauncher.ru
22
SSH
open
SSH-2.0-OpenSSH_5.3

xlauncher.ru
25
SMTP
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

xlauncher.ru
25
SMTP
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

xlauncher.ru
53
DNS
open


xlauncher.ru
53
DNS
open


xlauncher.ru
110
POP3
open
+OK Dovecot ready.

xlauncher.ru
110
POP3
open
+OK Dovecot ready.

xlauncher.ru
143
IMAP
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

xlauncher.ru
143
IMAP
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

xlauncher.ru
465
SMTP (encrypted)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500
Mail certificate is invalid
xlauncher.ru
465
SMTP (encrypted)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500
Mail certificate is invalid
xlauncher.ru
587
SMTP (encrypted, submission)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

xlauncher.ru
587
SMTP (encrypted, submission)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

xlauncher.ru
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Mail certificate is invalid
xlauncher.ru
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Mail certificate is invalid
xlauncher.ru
995
POP3 (encrypted)
open
+OK Dovecot ready.
Mail certificate is invalid
xlauncher.ru
995
POP3 (encrypted)
open
+OK Dovecot ready.
Mail certificate is invalid
xlauncher.ru
1433
MS SQL



xlauncher.ru
1433
MS SQL



xlauncher.ru
2082
cPanel (http)



xlauncher.ru
2082
cPanel (http)



xlauncher.ru
2083
cPanel (https)



xlauncher.ru
2083
cPanel (https)



xlauncher.ru
2086
WHM (http)



xlauncher.ru
2086
WHM (http)



xlauncher.ru
2087
WHM (https)



xlauncher.ru
2087
WHM (https)



xlauncher.ru
2089
cPanel Licensing



xlauncher.ru
2089
cPanel Licensing



xlauncher.ru
2095
cPanel Webmail (http)



xlauncher.ru
2095
cPanel Webmail (http)



xlauncher.ru
2096
cPanel Webmail (https)



xlauncher.ru
2096
cPanel Webmail (https)



xlauncher.ru
2222
DirectAdmin (http)



xlauncher.ru
2222
DirectAdmin (http)



xlauncher.ru
2222
DirectAdmin (https)



xlauncher.ru
2222
DirectAdmin (https)



xlauncher.ru
3306
mySql
open


xlauncher.ru
3306
mySql
open


xlauncher.ru
5224
Plesk Licensing



xlauncher.ru
5224
Plesk Licensing



xlauncher.ru
5432
PostgreSQL



xlauncher.ru
5432
PostgreSQL



xlauncher.ru
8080
Ookla Speedtest (http)



xlauncher.ru
8080
Ookla Speedtest (http)



xlauncher.ru
8080
Ookla Speedtest (https)



xlauncher.ru
8080
Ookla Speedtest (https)



xlauncher.ru
8083
VestaCP http
open
http://xlauncher.ru:8083/
Http-Status: 302
Redirect: https://xlauncher.ru:8083/
xlauncher.ru
8083
VestaCP http
open
http://xlauncher.ru:8083/
Http-Status: 302
Redirect: https://xlauncher.ru:8083/
xlauncher.ru
8083
VestaCP https
open
https://xlauncher.ru:8083/
Http-Status: 302
Certificate is invalid Redirect: /login/
xlauncher.ru
8083
VestaCP https
open
https://xlauncher.ru:8083/
Http-Status: 302
Certificate is invalid Redirect: /login/
xlauncher.ru
8443
Plesk Administration (https)



xlauncher.ru
8443
Plesk Administration (https)



xlauncher.ru
8447
Plesk Installer + Updates



xlauncher.ru
8447
Plesk Installer + Updates



xlauncher.ru
8880
Plesk Administration (http)



xlauncher.ru
8880
Plesk Administration (http)



xlauncher.ru
10000
Webmin (http)



xlauncher.ru
10000
Webmin (http)



xlauncher.ru
10000
Webmin (https)



xlauncher.ru
10000
Webmin (https)



41.216.191.154
21
FTP
open
220 (vsFTPd 2.2.2)

41.216.191.154
21
FTP
open
220 (vsFTPd 2.2.2)

41.216.191.154
22
SSH
open
SSH-2.0-OpenSSH_5.3

41.216.191.154
22
SSH
open
SSH-2.0-OpenSSH_5.3

41.216.191.154
25
SMTP
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

41.216.191.154
25
SMTP
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

41.216.191.154
53
DNS
open


41.216.191.154
53
DNS
open


41.216.191.154
110
POP3
open
+OK Dovecot ready.

41.216.191.154
110
POP3
open
+OK Dovecot ready.

41.216.191.154
143
IMAP
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

41.216.191.154
143
IMAP
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

41.216.191.154
465
SMTP (encrypted)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:55:07 -0500
Mail certificate is invalid
41.216.191.154
465
SMTP (encrypted)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:55:07 -0500
Mail certificate is invalid
41.216.191.154
587
SMTP (encrypted, submission)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

41.216.191.154
587
SMTP (encrypted, submission)
open
220 localhost.example.com ESMTP Exim 4.92.3 Fri, 14 Feb 2020 03:54:43 -0500

41.216.191.154
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Mail certificate is invalid
41.216.191.154
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Mail certificate is invalid
41.216.191.154
995
POP3 (encrypted)
open
+OK Dovecot ready.
Mail certificate is invalid
41.216.191.154
995
POP3 (encrypted)
open
+OK Dovecot ready.
Mail certificate is invalid
41.216.191.154
1433
MS SQL



41.216.191.154
1433
MS SQL



41.216.191.154
2082
cPanel (http)



41.216.191.154
2082
cPanel (http)



41.216.191.154
2083
cPanel (https)



41.216.191.154
2083
cPanel (https)



41.216.191.154
2086
WHM (http)



41.216.191.154
2086
WHM (http)



41.216.191.154
2087
WHM (https)



41.216.191.154
2087
WHM (https)



41.216.191.154
2089
cPanel Licensing



41.216.191.154
2089
cPanel Licensing



41.216.191.154
2095
cPanel Webmail (http)



41.216.191.154
2095
cPanel Webmail (http)



41.216.191.154
2096
cPanel Webmail (https)



41.216.191.154
2096
cPanel Webmail (https)



41.216.191.154
2222
DirectAdmin (http)



41.216.191.154
2222
DirectAdmin (http)



41.216.191.154
2222
DirectAdmin (https)



41.216.191.154
2222
DirectAdmin (https)



41.216.191.154
3306
mySql
open


41.216.191.154
3306
mySql
open


41.216.191.154
5224
Plesk Licensing



41.216.191.154
5224
Plesk Licensing



41.216.191.154
5432
PostgreSQL



41.216.191.154
5432
PostgreSQL



41.216.191.154
8080
Ookla Speedtest (http)



41.216.191.154
8080
Ookla Speedtest (http)



41.216.191.154
8080
Ookla Speedtest (https)



41.216.191.154
8080
Ookla Speedtest (https)



41.216.191.154
8083
VestaCP http
open
http://41.216.191.154:8083/
Http-Status: 302
Redirect: https://41.216.191.154:8083/
41.216.191.154
8083
VestaCP http
open
http://41.216.191.154:8083/
Http-Status: 302
Redirect: https://41.216.191.154:8083/
41.216.191.154
8083
VestaCP https
open
https://41.216.191.154:8083/
Http-Status: 302
Certificate is invalid Redirect: /login/
41.216.191.154
8083
VestaCP https
open
https://41.216.191.154:8083/
Http-Status: 302
Certificate is invalid Redirect: /login/
41.216.191.154
8443
Plesk Administration (https)



41.216.191.154
8443
Plesk Administration (https)



41.216.191.154
8447
Plesk Installer + Updates



41.216.191.154
8447
Plesk Installer + Updates



41.216.191.154
8880
Plesk Administration (http)



41.216.191.154
8880
Plesk Administration (http)



41.216.191.154
10000
Webmin (http)



41.216.191.154
10000
Webmin (http)



41.216.191.154
10000
Webmin (https)



41.216.191.154
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=5d0cb18a-1c65-4d7a-b02c-75ee8469d807


Last Result: https://check-your-website.server-daten.de/?q=xlauncher.ru - 2020-02-14 09:53:28


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

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