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


Update: 2020-03-04 - now 90 days later. All affected Letsencrypt certificates should be renewed. Time to remove that Info.




V

Connect failure - perhaps firewall

Checked:
07.04.2020 00:00:39


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
berianz.net
A
93.49.207.20
Rome/Latium/Italy (IT) - Fastweb SpA
No Hostname found
yes
1
0

AAAA

yes


www.berianz.net
C
ghs.googlehosted.com
yes
1
0

A
172.217.17.147
Amsterdam/North Holland/Netherlands (NL) - Google LLC
Hostname: ams15s30-in-f19.1e100.net
yes



AAAA
2a00:1450:400e:807::2013
Amsterdam/North Holland/Netherlands (NL) - GOOGLE-2a

yes


www.berianz.net
A
172.217.22.19
Frankfurt am Main/Hesse/Germany (DE) - Google LLC
No Hostname found
no


ghs.googlehosted.com
A
172.217.22.19
Frankfurt am Main/Hesse/Germany (DE) - Google LLC
No Hostname found
no



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 33853, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2020, 00:00:00 +, Signature-Inception: 01.04.2020, 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: net
net
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.04.2020, 17:00:00 +, Signature-Inception: 06.04.2020, 16:00:00 +, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24512, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.04.2020, 16:28:30 +, Signature-Inception: 04.04.2020, 16:23:30 +, KeyTag 35886, Signer-Name: net



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



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

Zone: berianz.net
berianz.net
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 13.04.2020, 11:54:52 +, Signature-Inception: 06.04.2020, 10:44:52 +, KeyTag 24512, Signer-Name: net



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 58294, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 27.04.2020, 11:54:51 +, Signature-Inception: 05.04.2020, 11:54:51 +, KeyTag 10289, Signer-Name: berianz.net



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



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



RRSIG Type 1, expiration 2020-04-27 11:54:51 + validates the A - Result: 93.49.207.20



RRSIG Type 50, expiration 2020-04-27 11:54:51 + validates the NSEC3 RR that proves the not-existence of the CNAME RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2020-04-27 11:54:51 + validates the NSEC3 RR that proves the not-existence of the TXT RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2020-04-27 11:54:51 + validates the NSEC3 RR that proves the not-existence of the AAAA RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2020-04-27 11:54:51 + validates the NSEC3 RR that proves the not-existence of the TLSA RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS



RRSIG Type 50, expiration 2020-04-27 11:54:51 + validates the NSEC3 RR that proves the not-existence of the CAA RR. Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS

Zone: www.berianz.net
www.berianz.net
0 DS RR in the parent zone found

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 33853, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2020, 00:00:00 +, Signature-Inception: 01.04.2020, 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



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.04.2020, 17:00:00 +, Signature-Inception: 06.04.2020, 16:00:00 +, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 56311, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2020, 18:24:21 +, Signature-Inception: 05.04.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2020, 18:24:21 +, Signature-Inception: 05.04.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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: googlehosted.com
googlehosted.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: ghs.googlehosted.com
ghs.googlehosted.com
0 DS RR in the parent zone found



0 DNSKEY RR found





3. Name Servers

DomainNameserverNS-IP
berianz.net
  ns-cloud-d1.googledomains.com
216.239.32.109
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:32::6d
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-d2.googledomains.com
216.239.34.109
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:34::6d
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-d3.googledomains.com
216.239.36.109
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:36::6d
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-d4.googledomains.com
216.239.38.109
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:38::6d
Ashburn/Virginia/United States (US) - Google LLC

net
  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


ghs.googlehosted.com
  ns1.google.com
216.239.32.10
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:32::a
Ashburn/Virginia/United States (US) - Google LLC

googlehosted.com
  ns1.google.com


  ns2.google.com


  ns3.google.com


  ns4.google.com

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:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1586210414
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


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


Domain:berianz.net
Zone-Name:
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:16
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8



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


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


Domain:googlehosted.com
Zone-Name:
Primary:ns1.google.com
Mail:dns-admin.google.com
Serial:304870938
Refresh:900
Retry:900
Expire:1800
TTL:60
num Entries:2


Domain:googlehosted.com
Zone-Name:
Primary:ns1.google.com
Mail:dns-admin.google.com
Serial:304988589
Refresh:900
Retry:900
Expire:1800
TTL:60
num Entries:2


Domain:ghs.googlehosted.com
Zone-Name:
Primary:ns1.google.com
Mail:dns-admin.google.com
Serial:304988589
Refresh:900
Retry:900
Expire:1800
TTL:60
num Entries:2


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://www.berianz.net/
172.217.17.147
302
http://berianz.net/
Html is minified: 101.41 %
0.080
D
Location: http://berianz.net/
Date: Mon, 06 Apr 2020 22:01:45 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 216
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://www.berianz.net/
172.217.22.19
302
http://berianz.net/
Html is minified: 101.41 %
0.080
D
Location: http://berianz.net/
Date: Mon, 06 Apr 2020 22:01:45 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 216
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://www.berianz.net/
2a00:1450:400e:807::2013
302
http://berianz.net/
Html is minified: 101.41 %
0.063
D
Location: http://berianz.net/
Date: Mon, 06 Apr 2020 22:01:45 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 216
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://berianz.net/
93.49.207.20
-2

1.117
V
ConnectFailure - Unable to connect to the remote server

• https://berianz.net/
93.49.207.20
-2

1.100
V
ConnectFailure - Unable to connect to the remote server

• https://www.berianz.net/
172.217.17.147
-4

0.110
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://www.berianz.net/
172.217.22.19
-4

0.116
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://www.berianz.net/
2a00:1450:400e:807::2013
-4

0.087
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://www.berianz.net:443/
172.217.17.147
-8

0.093
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.berianz.net:443/
172.217.22.19
-8

0.104
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.berianz.net:443/
2a00:1450:400e:807::2013
-8

0.087
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
172.217.17.147
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 101.06 %
0.087
D
Visible Content: 302 Moved 302 Moved The document has moved here .
Location: http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Date: Mon, 06 Apr 2020 22:01:48 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 285
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
172.217.22.19
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 101.06 %
0.077
D
Visible Content: 302 Moved 302 Moved The document has moved here .
Location: http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Date: Mon, 06 Apr 2020 22:01:48 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 285
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a00:1450:400e:807::2013
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 101.06 %
0.064
D
Visible Content: 302 Moved 302 Moved The document has moved here .
Location: http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Date: Mon, 06 Apr 2020 22:01:48 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 285
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

• http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
93.49.207.20
-2

1.110
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "berianz.net" is domain, public suffix is "net", 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.
CError - no version with Http-Status 200
Dhttp://www.berianz.net/ 172.217.17.147
302
http://berianz.net/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.berianz.net/ 172.217.22.19
302
http://berianz.net/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.berianz.net/ 2a00:1450:400e:807::2013
302
http://berianz.net/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.217.17.147
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.217.22.19
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1450:400e:807::2013
302
http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
Vhttp://berianz.net/ 93.49.207.20
-2

connect failure - perhaps firewall
Vhttps://berianz.net/ 93.49.207.20
-2

connect failure - perhaps firewall
Vhttp://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 93.49.207.20
-2

connect failure - perhaps firewall

2. DNS- and NameServer - Checks

AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns-cloud-d1.googledomains.com,ns-cloud-d2.googledomains.com,ns-cloud-d3.googledomains.com,ns-cloud-d4.googledomains.com
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
Agood: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates

3. Content- and Performance-critical Checks

http://berianz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 93.49.207.20
-2

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: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
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: 81386 milliseconds, 81.386 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 (alpha)

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
ghs.googlehosted.com
0

no CAA entry found
1
0
googlehosted.com
5
issue
pki.goog
1
0
www.berianz.net



1
0
berianz.net
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
berianz.net

ok
1
0
www.berianz.net


1
0
ghs.googlehosted.com

ok
1
0
_acme-challenge.berianz.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.berianz.net

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


1
0
_acme-challenge.berianz.net.berianz.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.berianz.net.berianz.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.berianz.net.www.berianz.net

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


1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c07ed9d6-ed49-4298-a374-e45000433f40


Last Result: https://check-your-website.server-daten.de/?q=berianz.net - 2020-04-07 00:00: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=berianz.net" target="_blank">Check this Site: berianz.net</a>