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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
02.12.2019 19:36:01


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
snorlaxcloud.duckdns.org
A
73.219.16.139
Beverly/Massachusetts/United States (US) - Comcast Cable Communications
Hostname: c-73-219-16-139.hsd1.ma.comcast.net
yes
1
0

AAAA

yes


www.snorlaxcloud.duckdns.org
A
73.219.16.139
Beverly/Massachusetts/United States (US) - Comcast Cable Communications
Hostname: c-73-219-16-139.hsd1.ma.comcast.net
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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2019, 17:00:00 +, Signature-Inception: 02.12.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)



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



4 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 11324, Flags 256



Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 41987, Flags 256



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.12.2019, 15:28:18 +, Signature-Inception: 01.12.2019, 14:28:18 +, KeyTag 9795, Signer-Name: org



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.12.2019, 15:28:18 +, Signature-Inception: 01.12.2019, 14:28:18 +, KeyTag 17883, Signer-Name: org



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.12.2019, 15:28:18 +, Signature-Inception: 01.12.2019, 14:28:18 +, KeyTag 41987, Signer-Name: org



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 41987 used to validate the DNSKEY RRSet



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



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: duckdns.org
duckdns.org
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 "mnorhcks4b6fjob5ap1mrs7utmhf26bm" between the hashed NSEC3-owner "mnoq314vn5m775pq7osblqq7jdr6o56r" and the hashed NextOwner "mnoum1prd3kbj2cugts7uugj1ccs2ipu". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner mnoq314vn5m775pq7osblqq7jdr6o56r.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.12.2019, 15:28:18 +, Signature-Inception: 01.12.2019, 14:28:18 +, KeyTag 41987, Signer-Name: org



0 DNSKEY RR found




Zone: snorlaxcloud.duckdns.org
snorlaxcloud.duckdns.org
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.snorlaxcloud.duckdns.org
www.snorlaxcloud.duckdns.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.snorlaxcloud.duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

snorlaxcloud.duckdns.org
U  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon Technologies Inc.


U  ns2.duckdns.org
54.191.117.119
Portland/Oregon/United States (US) - Amazon Technologies Inc.


U  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.

duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

org
  a0.org.afilias-nst.info / ns000a.app2.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 2.ber.pch


  b0.org.afilias-nst.org / ns000b.app12.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 5.fra.pch


  c0.org.afilias-nst.info / ns000b.app10.ams2.afilias-nst.info


  d0.org.afilias-nst.org / app1.iad1.hosts.meta.redstone.afilias-nst.info-2


4. SOA-Entries


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013726703
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.snorlaxcloud.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
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://snorlaxcloud.duckdns.org/
73.219.16.139
302
http://snorlaxcloud.duckdns.org/Main
Html is minified: 110.00 %
0.277
D
Server: nginx
Date: Mon, 02 Dec 2019 18:38:25 GMT
Content-Type: text/html
Content-Length: 154
Connection: close
Location: Main

• http://www.snorlaxcloud.duckdns.org/
73.219.16.139
302
http://www.snorlaxcloud.duckdns.org/Main
Html is minified: 110.00 %
0.276
D
Server: nginx
Date: Mon, 02 Dec 2019 18:38:26 GMT
Content-Type: text/html
Content-Length: 154
Connection: close
Location: Main

• http://snorlaxcloud.duckdns.org/Main

401

Html is minified: 108.05 %
0.323
M
Unauthorized
Server: nginx
Date: Mon, 02 Dec 2019 18:38:34 GMT
Content-Type: text/html
Content-Length: 188
Connection: close
WWW-Authenticate: Basic realm="unRAID",Basic realm="unRAID"

• http://www.snorlaxcloud.duckdns.org/Main

401

Html is minified: 108.05 %
1.987
M
Unauthorized
Server: nginx
Date: Mon, 02 Dec 2019 18:38:36 GMT
Content-Type: text/html
Content-Length: 188
Connection: close
WWW-Authenticate: Basic realm="unRAID",Basic realm="unRAID"

• https://snorlaxcloud.duckdns.org/
73.219.16.139
-2

3.800
V
ConnectFailure - Unable to connect to the remote server

• https://www.snorlaxcloud.duckdns.org/
73.219.16.139
-2

3.790
V
ConnectFailure - Unable to connect to the remote server

• http://snorlaxcloud.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
73.219.16.139
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.303
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Mon, 02 Dec 2019 18:38:34 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

• http://www.snorlaxcloud.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
73.219.16.139
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.277
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Mon, 02 Dec 2019 18:38:34 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "snorlaxcloud.duckdns.org" is domain, public suffix is "duckdns.org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
Agood: All ip addresses are public addresses
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 (4 urls)
http://snorlaxcloud.duckdns.org/Main


Url with incomplete Content-Type - header - missing charset
http://www.snorlaxcloud.duckdns.org/Main


Url with incomplete Content-Type - header - missing charset
http://snorlaxcloud.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 73.219.16.139


Url with incomplete Content-Type - header - missing charset
http://www.snorlaxcloud.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 73.219.16.139


Url with incomplete Content-Type - header - missing charset
CError - no version with Http-Status 200
Dhttp://snorlaxcloud.duckdns.org/ 73.219.16.139
302
http://snorlaxcloud.duckdns.org/Main
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.snorlaxcloud.duckdns.org/ 73.219.16.139
302
http://www.snorlaxcloud.duckdns.org/Main
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
Mhttp://snorlaxcloud.duckdns.org/Main
401

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://www.snorlaxcloud.duckdns.org/Main
401

Misconfiguration - main pages should never send http status 400 - 499
Vhttps://snorlaxcloud.duckdns.org/ 73.219.16.139
-2

connect failure - perhaps firewall
Vhttps://www.snorlaxcloud.duckdns.org/ 73.219.16.139
-2

connect failure - perhaps firewall
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 54.187.92.222: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 54.191.117.119: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 52.26.169.94:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 52.26.169.94: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 52.26.169.94:53

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: ns1.duckdns.org,ns2.duckdns.org,ns3.duckdns.org
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 54.191.117.119: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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: 170756 milliseconds, 170.756 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.snorlaxcloud.duckdns.org



1
0
snorlaxcloud.duckdns.org



1
0
duckdns.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
snorlaxcloud.duckdns.org

ok
1
0
www.snorlaxcloud.duckdns.org

ok
1
0
_acme-challenge.snorlaxcloud.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.www.snorlaxcloud.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.snorlaxcloud.duckdns.org.snorlaxcloud.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.snorlaxcloud.duckdns.org.snorlaxcloud.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.snorlaxcloud.duckdns.org.www.snorlaxcloud.duckdns.org

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=4b8f6c2f-0878-4d83-ba65-b2c314038325


Last Result: https://check-your-website.server-daten.de/?q=snorlaxcloud.duckdns.org - 2019-12-02 19:36:01


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

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