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




N

No trusted Certificate

Checked:
12.06.2019 05:53:40


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
103.7.41.38
A
103.7.41.38
/VN
Hostname: mx4138.superdata.vn
yes



2. DNSSEC


No DNSSEC - Informations found


3. Name Servers


No Nameserver entries found


4. SOA-Entries


No SOA entries found

5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://103.7.41.38/
103.7.41.38
-14

10.026
T
Timeout - The operation has timed out

• https://103.7.41.38/
103.7.41.38
200

2.606
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Wed, 12 Jun 2019 04:08:38 GMT
Server: Apache/2
Last-Modified: Thu, 06 Aug 2015 07:43:56 GMT
ETag: "d0d27-2c-51c9fae778700"
Accept-Ranges: bytes
Content-Length: 44
Vary: Accept-Encoding,User-Agent
Connection: close
Content-Type: text/html; charset=UTF-8

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

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

6. Comments


Aname "103.7.41.38" is ipv4 address, public suffix is not defined
Agood: All ip addresses are public addresses
Agood: destination is https
Agood - only one version with Http-Status 200
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://103.7.41.38/ 103.7.41.38
200

Missing HSTS-Header
Nhttps://103.7.41.38/ 103.7.41.38
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
OOld connection: Diffie-Hellman Key Exchange with 1024 Bit is unsecure. Update to 2048 Bit Key Exchange.
http://103.7.41.38/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.7.41.38
-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
ADuration: 27020 milliseconds, 27.020 seconds


7. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
103.7.41.38
103.7.41.38
443
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
103.7.41.38
103.7.41.38
443
Certificate/chain invalid and wrong name
Tls12
DiffieHellman
1024
Aes256
256
Sha384
error checking OCSP stapling
weak
Self signed certificate
1CN=localhost, OU=none, O=none, L=Sometown, C=US, emailAddress=webmaster@localhost


8. Certificates

1.
1.
E=webmaster@localhost, CN=localhost, OU=none, O=none, L=Sometown, S=Someprovince, C=US
05.03.2014
20.07.2041
expires in 7977 days

1.
1.
E=webmaster@localhost, CN=localhost, OU=none, O=none, L=Sometown, S=Someprovince, C=US
05.03.2014

20.07.2041
expires in 7977 days


KeyalgorithmRSA encryption ( bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:00FAC84DAEA0FF837C
Thumbprint:3C25DC08E955B22314B6BAAC5E4DF09A037A4B89
SHA256 / Certificate:tQoFXfvyEeEyjxry0LKpuwN5oLCuvAJ7rWG482nCOcU=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3d1847215a98377db828a8bcf9705fdce227020fad1adeed74598d0f4ec1370c
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.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


10. Html-Content - Entries

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


11. CAA - Entries

No CAA entries found


12. TXT - Entries

No TXT entries found


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=74014bd2-d6a3-498e-858d-f9e930b50414


Last Result: https://check-your-website.server-daten.de/?q=103.7.41.38 - 2019-06-12 05:53:40


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

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