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



W

wrong Web-Response

Checked:
24.05.2019 05:55:45


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
webdiz.men
A
173.249.57.101
Hostname: vmi187759.contaboserver.net
yes
1
0

AAAA

yes


www.webdiz.men
A
173.249.57.101
Hostname: vmi187759.contaboserver.net
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.06.2019, 00:00:00 +, Signature-Inception: 21.05.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: men
men
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner men., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.06.2019, 18:00:00 +, Signature-Inception: 23.05.2019, 17: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 21264, Flags 256



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



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



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner men., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 17.06.2019, 12:28:35 +, Signature-Inception: 18.05.2019, 12:15:14 +, KeyTag 21264, Signer-Name: men



RRSIG-Owner men., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 17.06.2019, 12:28:35 +, Signature-Inception: 18.05.2019, 12:15:14 +, KeyTag 30055, Signer-Name: men



RRSIG-Owner men., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 17.06.2019, 12:28:35 +, Signature-Inception: 18.05.2019, 12:15:14 +, KeyTag 31777, Signer-Name: men



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



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



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



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



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

Zone: webdiz.men
webdiz.men
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "mmlmkd5uf9a2kbqsatt7pffgk5jojoop" between the hashed NSEC3-owner "me6i14hcfba7rpunt9s94ienphhqbiio" and the hashed NextOwner "n4adfqnp7496egik2ah0h61q0ltrj359". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner me6i14hcfba7rpunt9s94ienphhqbiio.men., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 21.06.2019, 14:11:51 +, Signature-Inception: 22.05.2019, 13:56:22 +, KeyTag 21264, Signer-Name: men



0 DNSKEY RR found




Zone: www.webdiz.men
www.webdiz.men
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.webdiz.men
  ns1.contabo.net / m0882.contabo.net

webdiz.men
  ns1.contabo.net / m0882.contabo.net
79.143.182.242

 
2a02:c200:0:10::882:1

  ns2.contabo.net / m0891.contabo.net
178.238.234.231

 
2a02:c200:0:10::891:1
men
X  a.nic.men / dns1.sjc


  b.nic.men / dns3.ams


  c.nic.men / dns2.ams


  d.nic.men / dns1.ams


4. SOA-Entries


Domain:men
Zone-Name:
Primary:a.nic.men
Mail:support.ariservices.com
Serial:1558669211
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:4


Domain:webdiz.men
Zone-Name:
Primary:ns1.contabo.net
Mail:hostmaster.contabo.de
Serial:2019052202
Refresh:3600
Retry:7200
Expire:2419200
TTL:10800
num Entries:4


Domain:www.webdiz.men
Zone-Name:
Primary:ns1.contabo.net
Mail:hostmaster.contabo.de
Serial:2019052202
Refresh:3600
Retry:7200
Expire:2419200
TTL:10800
num Entries:1


5. Screenshots

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

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://webdiz.men/
173.249.57.101
301
https://webdiz.men/
0.080
A
Server: nginx/1.14.0
Date: Fri, 24 May 2019 03:56:05 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://webdiz.men/

• http://www.webdiz.men/
173.249.57.101
301
https://webdiz.men/
0.064
E
Server: nginx/1.14.0
Date: Fri, 24 May 2019 03:56:05 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://webdiz.men/

• https://webdiz.men/
173.249.57.101
-4

0.090
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

• https://www.webdiz.men/
173.249.57.101
-4

0.110
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

• http://webdiz.men:443/
173.249.57.101
-3

0.106
A
ReceiveFailure - The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Visible Content:

• http://www.webdiz.men:443/
173.249.57.101
-3

0.104
A
ReceiveFailure - The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Visible Content:

• http://www.webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
173.249.57.101
301
https://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.050
E
Visible Content:
Server: nginx/1.14.0
Date: Fri, 24 May 2019 03:56:06 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
173.249.57.101
404

0.047
A
Not Found
Visible Content:
Server: nginx/1.14.0
Date: Fri, 24 May 2019 03:56:06 GMT
Content-Type: text/html
Content-Length: 169
Connection: close

• https://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-4

0.113
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "webdiz.men" is domain, public suffix is "men", top-level-domain-type is "generic", tld-manager is "Exclusive Registry Limited"
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 (1 urls)
http://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 173.249.57.101


Url with incomplete Content-Type - header - missing charset
CError - no version with Http-Status 200
Ehttp://www.webdiz.men/ 173.249.57.101
301
https://webdiz.men/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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
XFatal error: Nameserver doesn't support TCP connection: a.nic.men: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host

2. 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): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: c.nic.men: 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 (dns2.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: d.nic.men: 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 (dns1.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.contabo.net: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (m0882.contabo.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.contabo.net / 79.143.182.242: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (m0882.contabo.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.contabo.net / 2a02:c200:0:10::882:1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (m0882.contabo.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.contabo.net / 178.238.234.231: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (m0891.contabo.net). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.contabo.net / 2a02:c200:0:10::891:1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (m0891.contabo.net). COOKIE: ok. 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.

3. Content- and Performance-critical Checks

https://webdiz.men/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-4

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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: 31190 milliseconds, 31.190 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

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

Small Code Update - wait one minute


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

No CRT - CT-Log entries found


11. Html-Content - Entries

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


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


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.webdiz.men
0

no CAA entry found
1
0
webdiz.men
0

no CAA entry found
1
0
men
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
webdiz.men

ok
1
0
www.webdiz.men

ok
1
0
_acme-challenge.webdiz.men

missing entry or wrong length
1
0
_acme-challenge.www.webdiz.men

missing entry or wrong length
1
0
_acme-challenge.webdiz.men.webdiz.men

perhaps wrong
1
0
_acme-challenge.www.webdiz.men.webdiz.men

perhaps wrong
1
0
_acme-challenge.www.webdiz.men.www.webdiz.men

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. 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=9dac30ce-04fc-4d10-aaea-97876fa3bd05


Last Result: https://check-your-website.server-daten.de/?q=webdiz.men - 2019-06-05 14:19:49


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

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

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