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



P

Tls-Protocol error

Checked:
13.08.2019 01:41:03


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
rancher2.gsffiscal.com.br
A
209.240.98.77
Latham/New York/United States (US) - Turnkey Internet Inc.
Hostname: 209-240-98-77.static.as40244.net
yes
1
0

AAAA

yes


www.rancher2.gsffiscal.com.br

Name Error
yes
1
0


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: 31.08.2019, 00:00:00 +, Signature-Inception: 10.08.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: br
br
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner br., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.08.2019, 17:00:00 +, Signature-Inception: 12.08.2019, 16: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 13, KeyTag 2471, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 13, KeyTag 22756, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner br., Algorithm: 13, 1 Labels, original TTL: 21600 sec, Signature-expiration: 25.08.2019, 12:00:00 +, Signature-Inception: 04.08.2019, 12:00:00 +, KeyTag 2471, Signer-Name: br



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



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

Zone: com.br
com.br
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 26.08.2019, 12:00:08 +, Signature-Inception: 12.08.2019, 11:00:08 +, KeyTag 22756, Signer-Name: br



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



2 DNSKEY RR found



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



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 26.08.2019, 23:40:08 +, Signature-Inception: 12.08.2019, 22:40:08 +, KeyTag 36262, Signer-Name: com.br



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



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 36262, DigestType 2 and Digest "/5O5VpfMiD3gxNUK+89Lq5siW0ftrGeHVyejMO4ahG4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gsffiscal.com.br
gsffiscal.com.br
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 "ch4brnh9hl1hll7ur6rf5sgjs4meaam8" between the hashed NSEC3-owner "ch4bls4jdsb8lklci5nn7p8o36gb30un" and the hashed NextOwner "ch4bvsfkmckhfjcje0gufs1h8dfrem7n". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ch4bls4jdsb8lklci5nn7p8o36gb30un.com.br., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 24.08.2019, 07:45:06 +, Signature-Inception: 10.08.2019, 06:45:06 +, KeyTag 36262, Signer-Name: com.br



0 DNSKEY RR found




Zone: rancher2.gsffiscal.com.br
rancher2.gsffiscal.com.br
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.rancher2.gsffiscal.com.br
www.rancher2.gsffiscal.com.br
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.rancher2.gsffiscal.com.br
  ns1.hoservers.com.br

rancher2.gsffiscal.com.br
  ns1.hoservers.com.br / server.hoservers.com.br
192.99.46.12
Montreal/Quebec/Canada (CA) - OVH SAS

gsffiscal.com.br
  ns1.hoservers.com.br / server.hoservers.com.br


  ns2.hoservers.com.br / server.hoservers.com.br

com.br
  a.dns.br / a8.a.dns.br


  b.dns.br / b3.b.dns.br


  c.dns.br / c8.c.dns.br


  d.dns.br / d3.d.dns.br


  e.dns.br / e4.e.dns.br


  f.dns.br / f3.f.dns.br

br
  a.dns.br / a8.a.dns.br


  b.dns.br / b7.b.dns.br


  c.dns.br / c6.c.dns.br


  d.dns.br / d5.d.dns.br


  e.dns.br / e5.e.dns.br


  f.dns.br / f1.f.dns.br


4. SOA-Entries


Domain:br
Zone-Name:
Primary:a.dns.br
Mail:hostmaster.registro.br
Serial:2019224568
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:6


Domain:com.br
Zone-Name:
Primary:a.dns.br
Mail:hostmaster.registro.br
Serial:2019224568
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:6


Domain:gsffiscal.com.br
Zone-Name:
Primary:ns1.hoservers.com.br
Mail:monitor.host-on.com.br
Serial:2019081001
Refresh:86400
Retry:7200
Expire:3600000
TTL:86400
num Entries:2


Domain:rancher2.gsffiscal.com.br
Zone-Name:
Primary:ns1.hoservers.com.br
Mail:monitor.host-on.com.br
Serial:2019081001
Refresh:86400
Retry:7200
Expire:3600000
TTL:86400
num Entries:1


Domain:www.rancher2.gsffiscal.com.br
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://rancher2.gsffiscal.com.br/
209.240.98.77
302
https://rancher2.gsffiscal.com.br/
0.190
A
Content-Type: text/html; charset=utf-8
Location: https://rancher2.gsffiscal.com.br/
Date: Mon, 12 Aug 2019 22:38:59 GMT
Content-Length: 57
Connection: close

• https://rancher2.gsffiscal.com.br/
209.240.98.77
-10

0.190
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• http://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
209.240.98.77
302
https://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.190
A
Visible Content:
Content-Type: text/html; charset=utf-8
Location: https://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Date: Mon, 12 Aug 2019 22:39:01 GMT
Content-Length: 126
Connection: close

• https://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-10

0.306
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "rancher2.gsffiscal.com.br" is subdomain, public suffix is "com.br", top-level-domain-type is "country-code", Country is Brazil, tld-manager is "Comite Gestor da Internet no Brasil"
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
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption
Phttps://rancher2.gsffiscal.com.br/ 209.240.98.77
-10

Error creating a TLS-Connection: TLSv1.2 and Cipher Suite ECDHE-RSA-AES128-GCM-SHA256 found. This tool uses TLSv1.2, but not that Cipher Suite. Add additional Cipher Suites.
Phttps://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-10

Error creating a TLS-Connection: No more details available.

2. DNS- and NameServer - Checks

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

3. Content- and Performance-critical Checks

https://rancher2.gsffiscal.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-10

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 78803 milliseconds, 78.803 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
5

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1062902992
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-09 23:51:46
2019-11-07 23:51:46
rancher2.gsffiscal.com.br - 1 entries


1060354325
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-08 01:34:53
2019-11-06 01:34:53
rancher2.gsffiscal.com.br - 1 entries


1060343844
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-08 01:24:32
2019-11-06 01:24:32
rancher2.gsffiscal.com.br - 1 entries


1061854403
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-08 01:21:51
2019-11-06 01:21:51
rancher2.gsffiscal.com.br - 1 entries


1060339069
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-08 01:20:25
2019-11-06 01:20:25
rancher2.gsffiscal.com.br - 1 entries



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
rancher2.gsffiscal.com.br
0

no CAA entry found
1
0
gsffiscal.com.br
0

no CAA entry found
1
0
com.br
0

no CAA entry found
1
0
br
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
gsffiscal.com.br
google-site-verification=--yvLbq5FXju_mP2GNHagwcnwhUgGLEXuxumHSqXoC4
ok
1
0
gsffiscal.com.br
v=spf1 +a +mx +ip4:192.99.46.12 +ip4:192.95.14.125 ~all
ok
1
0
rancher2.gsffiscal.com.br

ok
1
0
_acme-challenge.rancher2.gsffiscal.com.br

Name Error - The domain name does not exist
1
0
_acme-challenge.rancher2.gsffiscal.com.br.gsffiscal.com.br

Name Error - The domain name does not exist
1
0
_acme-challenge.rancher2.gsffiscal.com.br.rancher2.gsffiscal.com.br

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=81553608-7985-4bd2-b8ef-089943184f6e


Last Result: https://check-your-website.server-daten.de/?q=rancher2.gsffiscal.com.br - 2019-08-13 01:41:03


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

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