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




W

wrong Web-Response

Checked:
10.06.2019 17:47:22


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
timtam.ch
A
77.239.51.20
Solothurn/CH
Hostname: 20-51-239-77.dyn.cable.fcom.ch
yes
1
0

AAAA

yes


www.timtam.ch

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 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: ch
ch
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: 23.06.2019, 05:00:00, Signature-Inception: 10.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



3 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 11896, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 13, KeyTag 33507, Flags 256



Public Key with Algorithm 13, KeyTag 47413, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.07.2019, 10:09:09, Signature-Inception: 20.05.2019, 09:09:09, KeyTag 11896, Signer-Name: ch



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 11896 used to validate the DNSKEY RRSet



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

Zone: timtam.ch
timtam.ch
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.timtam.ch
www.timtam.ch
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.timtam.ch
  ns1.entrydns.net

timtam.ch
  ns1.entrydns.net / ns1.entrydns.net
45.55.7.138
San Francisco/California/US


  ns2.entrydns.net / ns4.entrydns.net
45.127.112.24
San Francisco/California/US


 
2620:95:4001::24
San Francisco/California/US

ch
  a.nic.ch / lako.switch.ch


  b.nic.ch / wako.switch.ch


  c.nic.ch


  d.nic.ch / ns.dns.br


  e.nic.ch / 8.fra.pch


  f.nic.ch / s2.amx


T  g.nic.ch


  h.nic.ch


4. SOA-Entries


Domain:ch
Primary:a.nic.ch
Mail:dns-operation.switch.ch
Serial:2019061017
Refresh:900
Retry:600
Expire:1123200
TTL:900
num Entries:8


Domain:timtam.ch
Primary:ns1.entrydns.net
Mail:tim.tamsel.gmx.ch
Serial:2019061099
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:3


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://timtam.ch:80/
77.239.51.20
200

0.140
H
Server: nginx
Date: Mon, 10 Jun 2019 15:48:11 GMT
Content-Type: text/html
Content-Length: 1554
Connection: close
Vary: Accept-Encoding,Accept-Encoding
Last-Modified: Thu, 01 Feb 2018 23:07:27 GMT
ETag: "612-5642ea8d1d833"
Accept-Ranges: bytes

• https://timtam.ch:80/
77.239.51.20
-4

0.123
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• http://timtam.ch:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
77.239.51.20
404

0.200
A
Not Found
Visible Content:
Server: nginx
Date: Mon, 10 Jun 2019 15:48:11 GMT
Content-Type: text/html
Content-Length: 11939
Connection: close
Vary: Accept-Encoding
ETag: "5cd4a4d8-2ea3"

6. Comments

Aname "timtam.ch" is domain, public suffix is "ch", top-level-domain-type is "country-code", Country is Switzerland, tld-manager is "SWITCH The Swiss Education & Research Network"
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
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)
http://timtam.ch:80/ 77.239.51.20


Url with incomplete Content-Type - header - missing charset
http://timtam.ch:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.239.51.20


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.
AGood: Nameserver supports TCP connections: 3 good Nameserver
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.entrydns.net
XNameserver Timeout checking EDNS512: g.nic.ch
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: g.nic.ch: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.entrydns.net: 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.
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: 49140 milliseconds, 49.140 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


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
timtam.ch
0

no CAA entry found
1
0
ch
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
timtam.ch

ok
1
0
_acme-challenge.timtam.ch

Name Error - The domain name does not exist
1
0
_acme-challenge.timtam.ch.timtam.ch

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=c166fc1e-f307-4c35-964a-cd8ef07e7698


Last Result: https://check-your-website.server-daten.de/?q=timtam.ch%3a80 - 2019-06-10 17:47:22


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

<a href="https://check-your-website.server-daten.de/?q=timtam.ch%3a80" target="_blank">Check this Site: timtam.ch:80</a>