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




N

No trusted Certificate

Checked:
12.06.2019 09:29:50


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
tarots-en-ligne.com
A
37.59.197.167
/Beau Vallon/SC
Hostname: 37-59-197-167.cinfuserver.com
yes
1
0

AAAA

yes


www.tarots-en-ligne.com
A
37.59.197.167
/Beau Vallon/SC
Hostname: 37-59-197-167.cinfuserver.com
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: com
com
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: 25.06.2019, 05:00:00, Signature-Inception: 12.06.2019, 04:00:00, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.06.2019, 18:25:33, Signature-Inception: 11.06.2019, 18:20:33, KeyTag 30909, Signer-Name: com



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



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

Zone: tarots-en-ligne.com
tarots-en-ligne.com
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.



0 DNSKEY RR found





Zone: www.tarots-en-ligne.com
www.tarots-en-ligne.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.tarots-en-ligne.com
  ns1.tarots-en-ligne.com

tarots-en-ligne.com
  ns1.tarots-en-ligne.com
37.59.197.167
/Beau Vallon/SC


  ns2.tarots-en-ligne.com
37.59.197.167
/Beau Vallon/SC

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1560324567
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1560324577
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:tarots-en-ligne.com
Primary:ns1.tarots-en-ligne.com
Mail:admin.tarots-en-ligne.com
Serial:2019061204
Refresh:3600
Retry:1800
Expire:604800
TTL:3600
num Entries:2


Domain:www.tarots-en-ligne.com
Primary:ns1.tarots-en-ligne.com
Mail:admin.tarots-en-ligne.com
Serial:2019061204
Refresh:3600
Retry:1800
Expire:604800
TTL:3600
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://tarots-en-ligne.com/
37.59.197.167
200

0.060
H
Content-Type: text/html
Accept-Ranges: bytes
ETag: "2560115172"
Last-Modified: Wed, 12 Jun 2019 06:39:35 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Content-Length: 2285
Connection: close
Date: Wed, 12 Jun 2019 07:30:26 GMT
Server: lighttpd/1.4.53

• http://www.tarots-en-ligne.com/
37.59.197.167
200

0.060
H
Content-Type: text/html
Accept-Ranges: bytes
ETag: "2560115172"
Last-Modified: Wed, 12 Jun 2019 06:39:35 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Content-Length: 2285
Connection: close
Date: Wed, 12 Jun 2019 07:30:26 GMT
Server: lighttpd/1.4.53

• https://tarots-en-ligne.com/
37.59.197.167
200

0.293
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Content-Type: text/html
Accept-Ranges: bytes
ETag: "2560115172"
Last-Modified: Wed, 12 Jun 2019 06:39:35 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=2592000; preload
Content-Length: 2285
Connection: close
Date: Wed, 12 Jun 2019 07:30:26 GMT
Server: lighttpd/1.4.53

• https://www.tarots-en-ligne.com/
37.59.197.167
200

0.303
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Content-Type: text/html
Accept-Ranges: bytes
ETag: "2560115172"
Last-Modified: Wed, 12 Jun 2019 06:39:35 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=2592000; preload
Content-Length: 2285
Connection: close
Date: Wed, 12 Jun 2019 07:30:27 GMT
Server: lighttpd/1.4.53

• http://tarots-en-ligne.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
37.59.197.167
404

0.054
A
Not Found
Visible Content:   Error 404 - Not Found The requested page could not be found but may be available again in the future  
Content-Type: text/html
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Content-Length: 2075
Connection: close
Date: Wed, 12 Jun 2019 07:30:27 GMT
Server: lighttpd/1.4.53

• http://www.tarots-en-ligne.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
37.59.197.167
404

0.057
A
Not Found
Visible Content:   Error 404 - Not Found The requested page could not be found but may be available again in the future  
Content-Type: text/html
X-Content-Type-Options: nosniff
X-XSS-Protection: 1;mode=block
X-Frame-Options: SAMEORIGIN
Access-Control-Allow-Origin: *
Content-Length: 2075
Connection: close
Date: Wed, 12 Jun 2019 07:30:27 GMT
Server: lighttpd/1.4.53

6. Comments

Aname "tarots-en-ligne.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
Agood: every https has a Strict Transport Security Header
Agood: HSTS has preload directive
AWarning: 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):0 complete Content-Type - header (6 urls)
http://tarots-en-ligne.com/ 37.59.197.167


Url with incomplete Content-Type - header - missing charset
http://www.tarots-en-ligne.com/ 37.59.197.167


Url with incomplete Content-Type - header - missing charset
https://tarots-en-ligne.com/ 37.59.197.167


Url with incomplete Content-Type - header - missing charset
https://www.tarots-en-ligne.com/ 37.59.197.167


Url with incomplete Content-Type - header - missing charset
http://tarots-en-ligne.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.59.197.167


Url with incomplete Content-Type - header - missing charset
http://www.tarots-en-ligne.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 37.59.197.167


Url with incomplete Content-Type - header - missing charset
Bwarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 2592000 seconds = 30 days found
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.
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
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.
Nhttps://tarots-en-ligne.com/ 37.59.197.167
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.tarots-en-ligne.com/ 37.59.197.167
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
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): 13 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.tarots-en-ligne.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.tarots-en-ligne.com / 37.59.197.167: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.tarots-en-ligne.com / 37.59.197.167: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: fatal timeout. CLIENTSUBNET: ok.
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: 36717 milliseconds, 36.717 seconds


7. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
tarots-en-ligne.com
37.59.197.167
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
tarots-en-ligne.com
37.59.197.167
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=Kloxo-MR certificate, emailAddress=ssl@mratwork.com
www.tarots-en-ligne.com
37.59.197.167
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
www.tarots-en-ligne.com
37.59.197.167
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=Kloxo-MR certificate, emailAddress=ssl@mratwork.com


8. Certificates

1.
1.
CN=Kloxo-MR certificate, E=ssl@mratwork.com
04.04.2017
11.03.2117
expires in 35604 days

1.
1.
CN=Kloxo-MR certificate, E=ssl@mratwork.com
04.04.2017

11.03.2117
expires in 35604 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00CE5745944D14928C
Thumbprint:A53C59D0EFCD0D9E54293FEED6FBCDD7F8749A1D
SHA256 / Certificate:SJCn4ycWk5uP6zIiN8fRhgNupuX98882bvjRCMPFQVE=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):defff70dbc916f48fcf78584aaeb763bf706ca54e2a7cf798869b8b4baec73ab
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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
3
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
961341919
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-11 06:27:55
2019-09-09 06:27:55
tarots-en-ligne.com, www.tarots-en-ligne.com - 2 entries


956221400
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-08 09:58:51
2019-09-06 09:58:51
mail.tarots-en-ligne.com, tarots-en-ligne.com, www.tarots-en-ligne.com - 3 entries


955732746
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-08 03:50:00
2019-09-06 03:50:00
mail.tarots-en-ligne.com, tarots-en-ligne.com, www.tarots-en-ligne.com - 3 entries


650742301
leaf cert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-11-30 00:00:00
2019-11-30 12:00:00
*.tarots-en-ligne.com, tarots-en-ligne.com - 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
3
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1565549525
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-11 04:27:55
2019-09-09 04:27:55
tarots-en-ligne.com, www.tarots-en-ligne.com
2 entries


1554810371
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-08 07:58:51
2019-09-06 07:58:51
mail.tarots-en-ligne.com, tarots-en-ligne.com, www.tarots-en-ligne.com
3 entries


1560017227
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-06-08 01:50:00
2019-09-06 01:50:00
mail.tarots-en-ligne.com, tarots-en-ligne.com, www.tarots-en-ligne.com
3 entries


993904443
leaf cert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2018-11-29 23:00:00
2019-11-30 11:00:00
*.tarots-en-ligne.com, tarots-en-ligne.com
2 entries



10. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://tarots-en-ligne.com/
37.59.197.167
a

1

0







img

2
7,560 Bytes
0
2
0




https://www.tarots-en-ligne.com/
37.59.197.167
a

1

0







img

2
7,560 Bytes
0
2
0




Details (GZip part is BETA, may be wrong / incomplete)

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://tarots-en-ligne.com/
37.59.197.167
a

http://mratwork.com/


1
ok



img
src
./images/kloxo-mr.png
200

1
ok



img
src
./images/logo.png
200

1
ok


https://www.tarots-en-ligne.com/
37.59.197.167
a

http://mratwork.com/


1
ok



img
src
./images/kloxo-mr.png
200

1
ok



img
src
./images/logo.png
200

1
ok



11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.tarots-en-ligne.com
0

no CAA entry found
1
0
tarots-en-ligne.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tarots-en-ligne.com

ok
1
0
www.tarots-en-ligne.com

ok
1
0
_acme-challenge.tarots-en-ligne.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tarots-en-ligne.com

Name Error - The domain name does not exist
1
0
_acme-challenge.tarots-en-ligne.com.tarots-en-ligne.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tarots-en-ligne.com.tarots-en-ligne.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tarots-en-ligne.com.www.tarots-en-ligne.com

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=7d83e095-67e5-4216-831a-2283b295b2ef


Last Result: https://check-your-website.server-daten.de/?q=tarots-en-ligne.com - 2019-06-12 09:29:50


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

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