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





1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
jira.wils.qmsaas.de
A
95.217.5.52
/FI
Hostname: static.52.5.217.95.clients.your-server.de
yes
1
0

AAAA
2a01:4f9:c010:5501::1
Gunzenhausen/Bayern/DE

yes


www.jira.wils.qmsaas.de
A
95.217.5.52
/FI
Hostname: static.52.5.217.95.clients.your-server.de
yes
1
0

AAAA
2a01:4f9:c010:5501::1
Gunzenhausen/Bayern/DE

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: de
de
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: 26.06.2019, 17:00:00, Signature-Inception: 13.06.2019, 16: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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 22771, Flags 256



Public Key with Algorithm 8, KeyTag 26298, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 20.06.2019, 12:00:00, Signature-Inception: 30.05.2019, 12:00:00, KeyTag 39227, Signer-Name: de



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



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

Zone: qmsaas.de
qmsaas.de
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: wils.qmsaas.de
wils.qmsaas.de
0 DS RR in the parent zone found

Zone: jira.wils.qmsaas.de
jira.wils.qmsaas.de
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.jira.wils.qmsaas.de
www.jira.wils.qmsaas.de
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.jira.wils.qmsaas.de
  ns1061.ui-dns.org / dns-pub-de-fra-fra302.server.lan

jira.wils.qmsaas.de
  ns1061.ui-dns.org / dns-pub-de-fra-fra302.server.lan
217.160.83.61
/DE


 
2001:8d8:fe:53:0:d9a0:533d:100
Karlsruhe/Baden-Wurttemberg/DE

wils.qmsaas.de
  ns1061.ui-dns.org

qmsaas.de
  ns1061.ui-dns.biz / dns-pub-de-fra-fra304.server.lan


  ns1061.ui-dns.com / dns-pub-de-fra-fra301.server.lan


  ns1061.ui-dns.de / dns-pub-de-fra-fra301.server.lan


  ns1061.ui-dns.org / dns-pub-de-fra-fra302.server.lan

de
  a.nic.de / ns-1.de.de8.bind


  f.nic.de / ns-2.de.de1.bind


  l.de.net / ns-2.de.fr1.bind


  n.de.net / s3.amx


  s.de.net / ns-2.de.de9.bind


  z.nic.de / ns-1.de.de8.bind


4. SOA-Entries


Domain:de
Primary:f.nic.de
Mail:its.denic.de
Serial:2019061381
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:qmsaas.de
Primary:ns1061.ui-dns.org
Mail:hostmaster.kundenserver.de
Serial:2016050602
Refresh:28800
Retry:7200
Expire:604800
TTL:300
num Entries:4


Domain:jira.wils.qmsaas.de
Primary:ns1061.ui-dns.org
Mail:hostmaster.kundenserver.de
Serial:2016050602
Refresh:28800
Retry:7200
Expire:604800
TTL:300
num Entries:2


Domain:www.jira.wils.qmsaas.de
Primary:ns1061.ui-dns.org
Mail:hostmaster.kundenserver.de
Serial:2016050602
Refresh:28800
Retry:7200
Expire:604800
TTL:300
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://jira.wils.qmsaas.de/
95.217.5.52
302
http://jira.wils.qmsaas.de/secure/SetupMode!default.jspa
0.077
D
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:15:24 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 0
Connection: close
X-AREQUESTID: 1155x293x1
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self'
Location: /secure/SetupMode!default.jspa

• http://jira.wils.qmsaas.de/
2a01:4f9:c010:5501::1
-14

10.030
T
Timeout - The operation has timed out

• http://www.jira.wils.qmsaas.de/
95.217.5.52
503

0.080
S
Service Temporarily Unavailable
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:15:25 GMT
Content-Type: text/html
Content-Length: 197
Connection: close

• http://www.jira.wils.qmsaas.de/
2a01:4f9:c010:5501::1
-14

10.017
T
Timeout - The operation has timed out

• http://jira.wils.qmsaas.de/secure/SetupMode!default.jspa

-14

10.016
T
Timeout - The operation has timed out

• https://jira.wils.qmsaas.de/
95.217.5.52
500

0.530
N
Internal Server Error
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:15:45 GMT
Content-Type: text/html
Content-Length: 177
Connection: close

• https://jira.wils.qmsaas.de/
2a01:4f9:c010:5501::1
-14

10.030
T
Timeout - The operation has timed out

• https://www.jira.wils.qmsaas.de/
95.217.5.52
503

0.563
N
Service Temporarily Unavailable
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:15:45 GMT
Content-Type: text/html
Content-Length: 197
Connection: close

• https://www.jira.wils.qmsaas.de/
2a01:4f9:c010:5501::1
-14

10.017
T
Timeout - The operation has timed out

• http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.217.5.52
404

0.093
A
Not Found
Visible Content: 404 Not Found nginx/1.17.0
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:16:06 GMT
Content-Type: text/html
Content-Length: 153
Connection: close

• http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a01:4f9:c010:5501::1
-14

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

• http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.217.5.52
503

0.076
S
Service Temporarily Unavailable
Visible Content: 503 Service Temporarily Unavailable nginx/1.17.0
Server: nginx/1.17.0
Date: Thu, 13 Jun 2019 19:16:06 GMT
Content-Type: text/html
Content-Length: 197
Connection: close

• http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a01:4f9:c010:5501::1
-14

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

6. Comments

Aname "jira.wils.qmsaas.de" is subdomain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
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):0 complete Content-Type - header (2 urls)
https://jira.wils.qmsaas.de/ 95.217.5.52


Url with incomplete Content-Type - header - missing charset
http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52


Url with incomplete Content-Type - header - missing charset
CError - no version with Http-Status 200
Dhttp://jira.wils.qmsaas.de/ 95.217.5.52
302
http://jira.wils.qmsaas.de/secure/SetupMode!default.jspa
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
Khttp://jira.wils.qmsaas.de/ 95.217.5.52, Status 302

http://jira.wils.qmsaas.de/ 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Khttp://www.jira.wils.qmsaas.de/ 95.217.5.52, Status 503

http://www.jira.wils.qmsaas.de/ 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Khttps://jira.wils.qmsaas.de/ 95.217.5.52, Status 500

https://jira.wils.qmsaas.de/ 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Khttps://www.jira.wils.qmsaas.de/ 95.217.5.52, Status 503

https://www.jira.wils.qmsaas.de/ 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Khttp://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52, Status 404

http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Khttp://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52, Status 503

http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1, Status -14
configuration problem - different ip addresses with different status
Nhttps://jira.wils.qmsaas.de/ 95.217.5.52
500

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.jira.wils.qmsaas.de/ 95.217.5.52
503

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): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1061.ui-dns.org: 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
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.
http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1
-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.
http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1
-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.
http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52
503

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1, Status -14

http://jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52, Status 404
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f9:c010:5501::1, Status -14

http://www.jira.wils.qmsaas.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.217.5.52, Status 503
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. 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: 99720 milliseconds, 99.720 seconds


7. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
jira.wils.qmsaas.de
95.217.5.52
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
jira.wils.qmsaas.de
95.217.5.52
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=letsencrypt-nginx-proxy-companion
www.jira.wils.qmsaas.de
95.217.5.52
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
www.jira.wils.qmsaas.de
95.217.5.52
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=letsencrypt-nginx-proxy-companion


8. Certificates

1.
1.
CN=letsencrypt-nginx-proxy-companion
11.06.2019
10.06.2020
expires in 267 days

1.
1.
CN=letsencrypt-nginx-proxy-companion
11.06.2019

10.06.2020
expires in 267 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:4C7DA7C80782BE3A10637D109A9D33103813968F
Thumbprint:F47720EC5DFC756882F6762A3AB5D9899C5B8744
SHA256 / Certificate:QUnwmA2UaYQaYAPD/iK30oNksL85qx711eKrLSxFB40=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):539ad3cfb0826eecff2923522a7c06c9e527620773974493e9bd5f65adc96fa5
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

DomainnameflagNameValue∑ Queries∑ Timeout
www.jira.wils.qmsaas.de
0

no CAA entry found
1
0
jira.wils.qmsaas.de
0

no CAA entry found
1
0
qmsaas.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
wils.qmsaas.de

Name Error - The domain name does not exist
1
0
jira.wils.qmsaas.de

ok
1
0
www.jira.wils.qmsaas.de

ok
1
0
_acme-challenge.jira.wils.qmsaas.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jira.wils.qmsaas.de

Name Error - The domain name does not exist
1
0
_acme-challenge.jira.wils.qmsaas.de.wils.qmsaas.de

Name Error - The domain name does not exist
1
0
_acme-challenge.jira.wils.qmsaas.de.jira.wils.qmsaas.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jira.wils.qmsaas.de.jira.wils.qmsaas.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jira.wils.qmsaas.de.www.jira.wils.qmsaas.de

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=a951a775-4ecc-4ceb-b149-1174646f277a


Last Result: https://check-your-website.server-daten.de/?q=jira.wils.qmsaas.de - 2019-06-13 21:14:58


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

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