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




V

Connect failure - perhaps firewall

Checked:
11.07.2019 17:48:22


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
bserv1.tk
A
95.216.168.177
Tuusula/Newland/Finland (FI) - HETZNER-DC
Hostname: static.177.168.216.95.clients.your-server.de
yes
1
0

AAAA

yes


www.bserv1.tk

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 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.08.2019, 00:00:00, Signature-Inception: 11.07.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: tk
tk
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner and the NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: bserv1.tk
bserv1.tk
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.bserv1.tk
www.bserv1.tk
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.bserv1.tk
  ns01.freenom.com

bserv1.tk
  ns01.freenom.com / aws2
54.171.131.39
Dublin/Leinster/Ireland (IE) - Amazon.com, Inc.


  ns02.freenom.com / NS0XPDNS
52.19.156.76
Dublin/Leinster/Ireland (IE) - Amazon.com, Inc.


  ns03.freenom.com / NS0XPDNS
104.155.27.112
Ashburn/Virginia/United States (US) - GOOGLE - Google LLC


  ns04.freenom.com / aws3
104.155.29.241
Ashburn/Virginia/United States (US) - GOOGLE - Google LLC

tk
  a.ns.tk / ams


  b.ns.tk / ams


  c.ns.tk / ams


  d.ns.tk / ams


4. SOA-Entries


Domain:tk
Primary:a.ns.tk
Mail:joost.zuurbier.dot.tk
Serial:1562859900
Refresh:10800
Retry:3600
Expire:604800
TTL:5
num Entries:1


Domain:tk
Primary:a.ns.tk
Mail:joost.zuurbier.dot.tk
Serial:1562859952
Refresh:10800
Retry:3600
Expire:604800
TTL:5
num Entries:3


Domain:bserv1.tk
Primary:ns01.freenom.com
Mail:soa.freenom.com
Serial:1562692502
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:4


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://bserv1.tk/
95.216.168.177
200

0.080
H
Server: nginx
Date: Thu, 11 Jul 2019 15:48:38 GMT
Content-Type: text/html
Content-Length: 1041
Last-Modified: Thu, 11 Jul 2019 15:40:58 GMT
Connection: close
Vary: Accept-Encoding
ETag: "5d27588a-411"
Accept-Ranges: bytes

• https://bserv1.tk/
95.216.168.177
-2

1.124
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 95.216.168.177:443

• http://bserv1.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.216.168.177
200

0.080
A
Visible Content:
Server: nginx
Date: Thu, 11 Jul 2019 15:48:40 GMT
Content-Type: text/plain
Content-Length: 86
Connection: close

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "bserv1.tk" is domain, public suffix is "tk", top-level-domain-type is "country-code", Country is Tokelau, tld-manager is "Telecommunication Tokelau Corporation (Teletok)"
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: 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://bserv1.tk/ 95.216.168.177


Url with incomplete Content-Type - header - missing charset
http://bserv1.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.216.168.177


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.
Vhttps://bserv1.tk/ 95.216.168.177
-2

connect failure - perhaps firewall
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): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns01.freenom.com: 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.
Ahttp://bserv1.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.216.168.177
200

Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. 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: 23376 milliseconds, 23.376 seconds


7. Connections (http/2 - check is BETA)

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
bserv1.tk
0

no CAA entry found
1
0
tk
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bserv1.tk

ok
1
0
_acme-challenge.bserv1.tk

Name Error - The domain name does not exist
1
0
_acme-challenge.bserv1.tk.bserv1.tk

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

Domain or IPPortDescriptionResultAnswer
bserv1.tk
21




bserv1.tk
21




bserv1.tk
22

open


bserv1.tk
22

open


bserv1.tk
25




bserv1.tk
25




bserv1.tk
53




bserv1.tk
53




bserv1.tk
110




bserv1.tk
110




bserv1.tk
143




bserv1.tk
143




bserv1.tk
465




bserv1.tk
465




bserv1.tk
587




bserv1.tk
587




bserv1.tk
993




bserv1.tk
993




bserv1.tk
995




bserv1.tk
995




bserv1.tk
1433




bserv1.tk
1433




bserv1.tk
2082




bserv1.tk
2082




bserv1.tk
2083




bserv1.tk
2083




bserv1.tk
2086




bserv1.tk
2086




bserv1.tk
2087




bserv1.tk
2087




bserv1.tk
2089




bserv1.tk
2089




bserv1.tk
3306

open


bserv1.tk
3306

open


bserv1.tk
5224




bserv1.tk
5224




bserv1.tk
5432




bserv1.tk
5432




bserv1.tk
8443




bserv1.tk
8443




bserv1.tk
8447




bserv1.tk
8447




bserv1.tk
8880




bserv1.tk
8880




95.216.168.177
21




95.216.168.177
21




95.216.168.177
22

open


95.216.168.177
22

open


95.216.168.177
25




95.216.168.177
25




95.216.168.177
53




95.216.168.177
53




95.216.168.177
110




95.216.168.177
110




95.216.168.177
143




95.216.168.177
143




95.216.168.177
465




95.216.168.177
465




95.216.168.177
587




95.216.168.177
587




95.216.168.177
993




95.216.168.177
993




95.216.168.177
995




95.216.168.177
995




95.216.168.177
1433




95.216.168.177
1433




95.216.168.177
2082




95.216.168.177
2082




95.216.168.177
2083




95.216.168.177
2083




95.216.168.177
2086




95.216.168.177
2086




95.216.168.177
2087




95.216.168.177
2087




95.216.168.177
2089




95.216.168.177
2089




95.216.168.177
3306

open


95.216.168.177
3306

open


95.216.168.177
5224




95.216.168.177
5224




95.216.168.177
5432




95.216.168.177
5432




95.216.168.177
8443




95.216.168.177
8443




95.216.168.177
8447




95.216.168.177
8447




95.216.168.177
8880




95.216.168.177
8880






Permalink: https://check-your-website.server-daten.de/?i=7f40d1f9-7a88-4169-aa64-9de361d048a4


Last Result: https://check-your-website.server-daten.de/?q=bserv1.tk - 2019-07-11 17:48: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=bserv1.tk" target="_blank">Check this Site: bserv1.tk</a>