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



V

Connect failure - perhaps firewall

Checked:
27.05.2019 21:48:11


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
rathe.app
A
34.66.242.178
Hostname: 178.242.66.34.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.rathe.app
A
34.66.242.178
Hostname: 178.242.66.34.bc.googleusercontent.com
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: app
app
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.06.2019, 17:00:00 +, Signature-Inception: 27.05.2019, 16: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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 63243, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 17.06.2019, 07:56:35 +, Signature-Inception: 26.05.2019, 07:56:35 +, KeyTag 23684, Signer-Name: app



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



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

Zone: rathe.app
rathe.app
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 "olftrtd0qa0k53g64fo3bi3805poicip" between the hashed NSEC3-owner "olftrtd0qa0k53g64fo3bi3805poicip" and the hashed NextOwner "olfuknhukkph2rv6cb5b5o908dcpbv8b". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner olftrtd0qa0k53g64fo3bi3805poicip.app., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.06.2019, 07:56:35 +, Signature-Inception: 26.05.2019, 07:56:35 +, KeyTag 63243, Signer-Name: app



0 DNSKEY RR found




Zone: www.rathe.app
www.rathe.app
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.rathe.app
  ns-cloud-e1.googledomains.com

rathe.app
  ns-cloud-e1.googledomains.com
216.239.32.110

 
2001:4860:4802:32::6e

  ns-cloud-e2.googledomains.com
216.239.34.110

 
2001:4860:4802:34::6e

  ns-cloud-e3.googledomains.com
216.239.36.110

 
2001:4860:4802:36::6e

  ns-cloud-e4.googledomains.com
216.239.38.110

 
2001:4860:4802:38::6e
app
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com


4. SOA-Entries


Domain:app
Zone-Name:
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:rathe.app
Zone-Name:
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.rathe.app
Zone-Name:
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
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://rathe.app/
34.66.242.178
200

0.236
H
Date: Mon, 27 May 2019 19:48:35 GMT
Server: Apache/2.4.25 (Debian)
Last-Modified: Mon, 27 May 2019 10:14:07 GMT
ETag: "509-589dbcf09e279"
Accept-Ranges: bytes
Content-Length: 1289
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://www.rathe.app/
34.66.242.178
200

0.236
H
Date: Mon, 27 May 2019 19:48:36 GMT
Server: Apache/2.4.25 (Debian)
Last-Modified: Mon, 27 May 2019 10:14:07 GMT
ETag: "509-589dbcf09e279"
Accept-Ranges: bytes
Content-Length: 1289
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• https://rathe.app/
34.66.242.178
-2

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

• https://www.rathe.app/
34.66.242.178
-2

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

• http://rathe.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.66.242.178
404

0.237
A
Not Found
Visible Content:
Date: Mon, 27 May 2019 19:48:39 GMT
Server: Apache/2.4.25 (Debian)
Content-Length: 342
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.rathe.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.66.242.178
404

0.240
A
Not Found
Visible Content:
Date: Mon, 27 May 2019 19:48:39 GMT
Server: Apache/2.4.25 (Debian)
Content-Length: 346
Connection: close
Content-Type: text/html; charset=iso-8859-1

7. Comments


1. General Results, most used to calculate the result

Aname "rathe.app" is domain, public suffix is "app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc."
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AExcellent: Domain is in the Google-Preload-List
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls)
http://rathe.app/ 34.66.242.178


Url with incomplete Content-Type - header - missing charset
http://www.rathe.app/ 34.66.242.178


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.
Vhttps://rathe.app/ 34.66.242.178
-2

connect failure - perhaps firewall
Vhttps://www.rathe.app/ 34.66.242.178
-2

connect failure - perhaps firewall

2. DNS- and NameServer - Checks

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

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: 29454 milliseconds, 29.454 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)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
2
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
876441482
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-23 00:22:25
2019-07-22 00:22:25
www.rathe.app - 1 entries


876424984
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-23 00:09:06
2019-07-22 00:09:06
rathe.app - 1 entries


814345139
leaf cert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-03-16 00:00:00
2020-03-16 12:00:00
*.rathe.app, rathe.app, sni.cloudflaressl.com - 3 entries



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

Issuerlast 7 daysactivenum Certs
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1308415404
leaf cert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-03-15 23:00:00
2020-03-16 11:00:00
*.rathe.app, rathe.app, sni.cloudflaressl.com
3 entries



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.rathe.app
0

no CAA entry found
1
0
rathe.app
0

no CAA entry found
1
0
app
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
rathe.app

ok
1
0
www.rathe.app

ok
1
0
_acme-challenge.rathe.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rathe.app

Name Error - The domain name does not exist
1
0
_acme-challenge.rathe.app.rathe.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rathe.app.rathe.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.rathe.app.www.rathe.app

Name Error - The domain name does not exist
1
0


15. 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=f637725a-077c-4850-9570-c55c672fb805


Last Result: https://check-your-website.server-daten.de/?q=rathe.app - 2019-05-27 21:48:11


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

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