T

Timeout

Checked:
15.05.2019 17:15:39


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
ousegarer.tk
A
195.20.41.26
No Hostname found
yes
1
0

AAAA

yes


www.ousegarer.tk
C
ousegarer.tk
yes
1
0

A
195.20.41.26
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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.06.2019, 00:00:00, Signature-Inception: 11.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
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


ousegarer.tk
0 DS RR in the parent zone found

0 DNSKEY RR found


www.ousegarer.tk
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
ousegarer.tk
  a.ns.tk
194.0.38.1

 
2001:678:50::1
tk
  a.ns.tk


  b.ns.tk


  c.ns.tk


  d.ns.tk


4. SOA-Entries


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


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


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


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


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://ousegarer.tk/
195.20.41.26
200

0.070
H
Server: nginx
Date: Wed, 15 May 2019 15:15:52 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 1101
Connection: close
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Pragma: no-cache
Set-Cookie: JSESSIONID=750CF235F90BADCDC7C72E45EE945548; Path=/; Domain=ousegarer.tk; HttpOnly
Vary: Accept-Encoding
X-Server: ip-172-30-0-72

• http://www.ousegarer.tk/
195.20.41.26
200

0.594
H
Server: nginx
Date: Wed, 15 May 2019 15:15:52 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 1101
Connection: close
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Pragma: no-cache
Set-Cookie: JSESSIONID=1421CBAE86E9857957BA91D1B7CD7710; Path=/; Domain=www.ousegarer.tk; HttpOnly
Vary: Accept-Encoding
X-Server: ip-172-30-0-72

• https://ousegarer.tk/
195.20.41.26
-14

10.027
T
Timeout - The operation has timed out

• https://www.ousegarer.tk/
195.20.41.26
-14

10.030
T
Timeout - The operation has timed out

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

0.073

Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> ousegarer.tk
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> <html> <head> <title>ousegarer.tk</title> <meta name="description" content="ousegarer.tk"> <meta name="keywords" content="ousegarer.tk"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-23441223-3']); _gaq.push(['_setDomainName', 'none']); _gaq.push(['_setAllowLinker', true]); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script> </head> <frameset rows="*"> <frame frameborder=0 src="http://51.75.255.83" name="dot_tk_frame_content" scrolling="auto" noresize> </frameset> </html>
Server: nginx
Date: Wed, 15 May 2019 15:16:13 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 1101
Connection: close
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Pragma: no-cache
Set-Cookie: JSESSIONID=A149F367B6B76A951FEB345D535DDCFB; Path=/; Domain=ousegarer.tk; HttpOnly
Vary: Accept-Encoding
X-Server: ip-172-30-2-18

• http://www.ousegarer.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
195.20.41.26
200

0.597

Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> ousegarer.tk
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> <html> <head> <title>ousegarer.tk</title> <meta name="description" content="ousegarer.tk"> <meta name="keywords" content="ousegarer.tk"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-23441223-3']); _gaq.push(['_setDomainName', 'none']); _gaq.push(['_setAllowLinker', true]); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script> </head> <frameset rows="*"> <frame frameborder=0 src="http://51.75.255.83" name="dot_tk_frame_content" scrolling="auto" noresize> </frameset> </html>
Server: nginx
Date: Wed, 15 May 2019 15:16:13 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 1101
Connection: close
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Pragma: no-cache
Set-Cookie: JSESSIONID=F172DF931224E8DBB5EA1643CD6B1FCC; Path=/; Domain=www.ousegarer.tk; HttpOnly
Vary: Accept-Encoding
X-Server: ip-172-30-2-18

6. Comments

Aname "ousegarer.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
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
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.
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: 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
XFatal error: Nameservers mit different SOA Serial Numbers
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate
http://ousegarer.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.20.41.26
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html
http://www.ousegarer.tk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.20.41.26
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html
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: 34290 milliseconds, 34.290 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 (BETA)

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 (BETA - mixed content and other checks)

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.ousegarer.tk



1
0
ousegarer.tk
0

no CAA entry found
1
0
tk
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ousegarer.tk

ok
1
0
www.ousegarer.tk


1
0
_acme-challenge.ousegarer.tk


1
0
_acme-challenge.www.ousegarer.tk


1
0
_acme-challenge.ousegarer.tk.ousegarer.tk


1
0
_acme-challenge.www.ousegarer.tk.ousegarer.tk


1
0
_acme-challenge.www.ousegarer.tk.www.ousegarer.tk


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=5fae495c-1da2-43f1-8c12-b8f634f65ec9


Last Result: https://check-your-website.server-daten.de/?q=ousegarer.tk - 2019-05-15 17:15:39


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

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