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



V

Connect failure - perhaps firewall

Checked:
22.09.2022 23:09:41


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
foxhill67.duckdns.org
A
82.75.177.212
Zwolle/Overijssel/Netherlands (NL) - Vodafone Ziggo
Hostname: 82-75-177-212.cable.dynamic.v4.ziggo.nl
yes
1
0

AAAA
2001:1c06:2d00:0:c497:7653:8e74:54ab
Zwolle/Overijssel/Netherlands (NL) - Vodafone Ziggo

yes


www.foxhill67.duckdns.org
A
82.75.177.212
Zwolle/Overijssel/Netherlands (NL) - Vodafone Ziggo
Hostname: 82-75-177-212.cable.dynamic.v4.ziggo.nl
yes
1
0

AAAA
2001:1c06:2d00:0:c497:7653:8e74:54ab
Zwolle/Overijssel/Netherlands (NL) - Vodafone Ziggo

yes


*.foxhill67.duckdns.org
A
82.75.177.212
yes



AAAA
2001:1c06:2d00:0:c497:7653:8e74:54ab
yes



CNAME

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 18733, Flags 256



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



Public Key with Algorithm 8, KeyTag 20826, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.10.2022, 16:00:00 +, Signature-Inception: 22.09.2022, 15:00:00 +, KeyTag 20826, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 29166, Flags 256



Public Key with Algorithm 8, KeyTag 56124, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2022, 15:23:54 +, Signature-Inception: 17.09.2022, 14:23:54 +, KeyTag 26974, Signer-Name: org



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest "T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=" 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 "6fabb6hcuj19tgg44lr37hr00rdj3gvl" between the hashed NSEC3-owner "6fab725nvaq3den222549c33aceptsil" and the hashed NextOwner "6fai2n79iic0ks7ua57l1vc1pssik70g". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 6fab725nvaq3den222549c33aceptsil.org., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2022, 15:23:54 +, Signature-Inception: 17.09.2022, 14:23:54 +, KeyTag 56124, Signer-Name: org



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "gdtpongmpok61u9lvnipqor8lra9l4t0" as Owner. That's the Hash of "org" with the NextHashedOwnerName "gdtrea8kmj2rneqen4m2ogj26kfsukj7". So that domain name is the Closest Encloser of "duckdns.org". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner gdtpongmpok61u9lvnipqor8lra9l4t0.org., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.10.2022, 21:05:46 +, Signature-Inception: 22.09.2022, 20:05:46 +, KeyTag 56124, Signer-Name: org



0 DNSKEY RR found




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



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.foxhill67.duckdns.org
  ns1.duckdns.org


  ns2.duckdns.org


  ns3.duckdns.org


  ns4.duckdns.org


  ns5.duckdns.org


  ns6.duckdns.org

foxhill67.duckdns.org
  ns1.duckdns.org
99.79.143.35
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.


  ns2.duckdns.org
35.182.183.211
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns3.duckdns.org
35.183.157.249
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns4.duckdns.org
3.97.51.116
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns5.duckdns.org
99.79.16.64
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.


  ns6.duckdns.org
3.97.58.28
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.

duckdns.org
  ns1.duckdns.org
99.79.143.35
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.


  ns2.duckdns.org
35.182.183.211
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns3.duckdns.org
35.183.157.249
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns4.duckdns.org
3.97.51.116
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.


  ns5.duckdns.org
99.79.16.64
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.


  ns6.duckdns.org
3.97.58.28
Toronto/Ontario/Canada (CA) - Amazon Technologies Inc.

org
  a0.org.afilias-nst.info


  a2.org.afilias-nst.info


  b0.org.afilias-nst.org


  b2.org.afilias-nst.org


  c0.org.afilias-nst.info


  d0.org.afilias-nst.org


4. SOA-Entries


Domain:org
Zone-Name:org
Primary:a0.org.afilias-nst.info
Mail:hostmaster.donuts.email
Serial:1663880362
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:6


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


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


Domain:www.foxhill67.duckdns.org
Zone-Name:duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2022061901
Refresh:6000
Retry:120
Expire:2419200
TTL:600
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://foxhill67.duckdns.org/
82.75.177.212 No GZip used - 26082 / 117856 - 22.13 % possible
200

Html is minified: 565.09 %
1.010
H
Content-type: text/html
Expires: 0

• http://foxhill67.duckdns.org/
2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

10.030
T
Timeout - The operation has timed out

• http://www.foxhill67.duckdns.org/
82.75.177.212 No GZip used - 26082 / 117856 - 22.13 % possible
200

Html is minified: 565.09 %
0.584
H
Content-type: text/html
Expires: 0

• http://www.foxhill67.duckdns.org/
2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

10.033
T
Timeout - The operation has timed out

• https://foxhill67.duckdns.org/
82.75.177.212
-2

1.097
V
ConnectFailure - Unable to connect to the remote server

• https://foxhill67.duckdns.org/
2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

1.114
V
ConnectFailure - Unable to connect to the remote server

• https://www.foxhill67.duckdns.org/
82.75.177.212
-2

1.107
V
ConnectFailure - Unable to connect to the remote server

• https://www.foxhill67.duckdns.org/
2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

1.117
V
ConnectFailure - Unable to connect to the remote server

• http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
82.75.177.212
200

Html is minified: 100.00 %
0.317

Visible Content: The requested URL was not found on this server
Content-type: text/html
Expires: 0

• http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
82.75.177.212
200

Html is minified: 100.00 %
0.183

Visible Content: The requested URL was not found on this server
Content-type: text/html
Expires: 0

• http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

10.040
T
Timeout - The operation has timed out
Visible Content:

• https://82.75.177.212/
82.75.177.212
-2

1.126
V
ConnectFailure - Unable to connect to the remote server

• https://[2001:1c06:2d00:0000:c497:7653:8e74:54ab]/
2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

1.116
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "foxhill67.duckdns.org" is domain, public suffix is ".duckdns.org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 6491 (complete: 199710)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: foxhill67.duckdns.org has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.foxhill67.duckdns.org has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: foxhill67.duckdns.org has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.foxhill67.duckdns.org has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
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://foxhill67.duckdns.org/ 82.75.177.212


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


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


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


Url with incomplete Content-Type - header - missing charset
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.
Khttp://foxhill67.duckdns.org/ 82.75.177.212, Status 200

http://foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.foxhill67.duckdns.org/ 82.75.177.212, Status 200

http://www.foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14
Configuration problem - different ip addresses with different status
Khttp://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200

http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200

http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14
Configuration problem - different ip addresses with different status
Vhttps://foxhill67.duckdns.org/ 82.75.177.212
-2

Connect failure - perhaps firewall
Vhttps://foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

Connect failure - perhaps firewall
Vhttps://www.foxhill67.duckdns.org/ 82.75.177.212
-2

Connect failure - perhaps firewall
Vhttps://www.foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

Connect failure - perhaps firewall
Vhttps://82.75.177.212/ 82.75.177.212
-2

Connect failure - perhaps firewall
Vhttps://[2001:1c06:2d00:0000:c497:7653:8e74:54ab]/ 2001:1c06:2d00:0:c497:7653:8e74:54ab
-2

Connect failure - perhaps firewall
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 99.79.143.35: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 35.182.183.211: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 35.183.157.249: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns4.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns4.duckdns.org / 3.97.51.116: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns5.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns5.duckdns.org / 99.79.16.64: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns6.duckdns.org: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns6.duckdns.org / 3.97.58.28: Timeout
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain foxhill67.duckdns.org, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.foxhill67.duckdns.org, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain foxhill67.duckdns.org, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.foxhill67.duckdns.org, 2 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.duckdns.org (99.79.143.35), ns2.duckdns.org (35.182.183.211), ns3.duckdns.org (35.183.157.249), ns4.duckdns.org (3.97.51.116), ns5.duckdns.org (99.79.16.64), ns6.duckdns.org (3.97.58.28)
AGood (1 - 3.0):: An average of 0.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 6 different Name Servers found: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, 6 Name Servers included in Delegation: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, 6 Name Servers included in 1 Zone definitions: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, 1 Name Servers listed in SOA.Primary: ns1.duckdns.org.
AGood: Only one SOA.Primary Name Server found.: ns1.duckdns.org.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.duckdns.org.
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, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 6 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 6 Name Servers, 1 Top Level Domain: duckdns.org
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used:
Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: CA
AInfo: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 3., 35., 99., 4 different subnets (first two Bytes): 3.97., 35.182., 35.183., 99.79., 6 different subnets (first three Bytes): 3.97.51., 3.97.58., 35.182.183., 35.183.157., 99.79.143., 99.79.16.
AGood: Name Server IPv4-addresses from different subnet found:
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: 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://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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.
http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. 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.
http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14

http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14

http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 1418330 milliseconds, 1418.330 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=R3, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4158733594
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-09-09 16:23:33
2022-12-08 16:23:32
foxhill67.duckdns.org - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7507186289
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-09-09 14:23:33
2022-12-08 15:23:32
foxhill67.duckdns.org
1 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: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org

QNr.DomainTypeNS used
1
org
NS
b.root-servers.net (2001:500:200::b)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
2
ns1.duckdns.org: 99.79.143.35
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns2.duckdns.org
35.182.183.211

Answer: ns3.duckdns.org
35.183.157.249

Answer: ns4.duckdns.org
3.97.51.116

Answer: ns5.duckdns.org
99.79.16.64

Answer: ns6.duckdns.org
3.97.58.28


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.foxhill67.duckdns.org



1
0
foxhill67.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
foxhill67.duckdns.org

ok
1
0
www.foxhill67.duckdns.org

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

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

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

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

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

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

foxhill67.duckdns.org
50
foxhill67.duckdns.org
0
1
1
The value of a MX record must have A / AAAA records. A CNAME is not allowed. See RFC 2181, 10.3. Two options: The owner of that zone has created a CNAME. Or the NameServer-software is fatal buggy, sends an answer asked CNAME.

CNAME



0
1
ok

MX

www.foxhill67.duckdns.org
50
www.foxhill67.duckdns.org
0
1
1
The value of a MX record must have A / AAAA records. A CNAME is not allowed. See RFC 2181, 10.3. Two options: The owner of that zone has created a CNAME. Or the NameServer-software is fatal buggy, sends an answer asked CNAME.

CNAME



0
1
ok

_dmarc
TXT
_dmarc.foxhill67.duckdns.org


0
1
ok



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=ce3709a6-2e71-4b6d-9088-a25d865cf26c


Last Result: https://check-your-website.server-daten.de/?q=foxhill67.duckdns.org - 2022-09-22 23:09:41


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro