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




Q

http sent over port 443

Checked:
11.09.2019 08:16:41


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
freadee.com
A
46.101.226.44
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC
No Hostname found
yes
2
0

AAAA

yes


www.freadee.com
CNAME
freadee.com
yes
1
0

A
46.101.226.44
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC
No Hostname found
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 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.09.2019, 05:00:00 +, Signature-Inception: 11.09.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 59944 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.09.2019, 18:25:33 +, Signature-Inception: 09.09.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com



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



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

Zone: freadee.com
freadee.com
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 "0qv7gc2eru2lhe8rqglhoo3r5k4ec18m" between the hashed NSEC3-owner "0qv6n1tju5v937cmo5huht0aoqc8tmot" and the hashed NextOwner "0qv7sa74o5v8g6mrbfi00hsl01omikq3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 0qv6n1tju5v937cmo5huht0aoqc8tmot.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.09.2019, 04:30:32 +, Signature-Inception: 09.09.2019, 03:20:32 +, KeyTag 17708, Signer-Name: com



0 DNSKEY RR found




Zone: www.freadee.com
www.freadee.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
freadee.com
  ns1.digitalocean.com / 67m22
173.245.58.51
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns2.digitalocean.com / 67m14
173.245.59.41
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns3.digitalocean.com / 67m28
198.41.222.173
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
Columbus/North Carolina/United States (US) - CLOUDFLARE

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1568182574
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1568182594
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


Domain:freadee.com
Zone-Name:
Primary:ns1.digitalocean.com
Mail:hostmaster.freadee.com
Serial:1556200379
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


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://freadee.com/
46.101.226.44 No GZip used - 2122 / 6159 - 34.45 % possible
200

Html is minified: 146.19 %
0.044
H
Content-Type: text/html
Date: Wed, 11 Sep 2019 06:17:11 GMT
Connection: close
Transfer-Encoding: chunked

• http://www.freadee.com/
46.101.226.44 No GZip used - 2122 / 6159 - 34.45 % possible
200

Html is minified: 146.19 %
0.040
H
Content-Type: text/html
Date: Wed, 11 Sep 2019 06:17:11 GMT
Connection: close
Transfer-Encoding: chunked

• https://freadee.com/
46.101.226.44
-4

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

• https://www.freadee.com/
46.101.226.44
-4

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

• http://freadee.com:443/
46.101.226.44 GZip used - 3138 / 10918 - 71.26 %
200

Html is minified: 148.83 %
0.054
Q
Visible Content:
Date: Wed, 11 Sep 2019 06:17:12 GMT
Server: Apache/2.4.38 (Ubuntu)
Last-Modified: Sat, 27 Apr 2019 06:40:14 GMT
ETag: "2aa6-5877d52de1f1b-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3138
Connection: close
Content-Type: text/html

• http://www.freadee.com:443/
46.101.226.44 GZip used - 3138 / 10918 - 71.26 %
200

Html is minified: 148.83 %
0.043
Q
Visible Content:
Date: Wed, 11 Sep 2019 06:17:12 GMT
Server: Apache/2.4.38 (Ubuntu)
Last-Modified: Sat, 27 Apr 2019 06:40:14 GMT
ETag: "2aa6-5877d52de1f1b-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3138
Connection: close
Content-Type: text/html

• http://freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
46.101.226.44 No GZip used - 2122 / 6159 - 34.45 % possible
200

Html is minified: 146.19 %
0.050

Visible Content:
Content-Type: text/html
Date: Wed, 11 Sep 2019 06:17:12 GMT
Connection: close
Transfer-Encoding: chunked

• http://www.freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
46.101.226.44 No GZip used - 2122 / 6159 - 34.45 % possible
200

Html is minified: 146.19 %
0.040

Visible Content:
Content-Type: text/html
Date: Wed, 11 Sep 2019 06:17:12 GMT
Connection: close
Transfer-Encoding: chunked

7. Comments


1. General Results, most used to calculate the result

Aname "freadee.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (6 urls)
http://freadee.com/ 46.101.226.44


Url with incomplete Content-Type - header - missing charset
http://freadee.com:443/ 46.101.226.44


Url with incomplete Content-Type - header - missing charset
http://www.freadee.com:443/ 46.101.226.44


Url with incomplete Content-Type - header - missing charset
http://www.freadee.com/ 46.101.226.44


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


Url with incomplete Content-Type - header - missing charset
http://www.freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.226.44


Url with incomplete Content-Type - header - missing 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.
Ihttp://freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.226.44
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Ihttp://www.freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.226.44
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Qhttp://freadee.com:443/ 46.101.226.44
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
Qhttp://www.freadee.com:443/ 46.101.226.44
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
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

http://freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.226.44
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 Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.freadee.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.101.226.44
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 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: 41673 milliseconds, 41.673 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)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 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.freadee.com



1
0
freadee.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
freadee.com

ok
1
0
www.freadee.com


1
0
_acme-challenge.freadee.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.freadee.com

Name Error - The domain name does not exist
1
0
_acme-challenge.freadee.com.freadee.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.freadee.com.freadee.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.freadee.com.www.freadee.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=d81fec69-b774-4bed-a82b-1f498076de49


Last Result: https://check-your-website.server-daten.de/?q=freadee.com - 2019-09-11 09:52:08


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

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