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


 

 

X

 

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

 

Checked:
03.02.2025 23:03:57

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
dayfin.ddns.net
A
136.33.163.240
Kansas City/Kansas/United States (US) - Google Fiber Inc.
Hostname: 136-33-163-240.googlefiber.net
yes
1
0

AAAA

yes


www.dayfin.ddns.net

Name Error
yes
1
0
*.dayfin.ddns.net
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 26470, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.02.2025, 00:00:00 +, Signature-Inception: 31.01.2025, 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






DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.02.2025, 17:00:00 +, Signature-Inception: 03.02.2025, 16:00:00 +, KeyTag 26470, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 10024, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.02.2025, 15:10:35 +, Signature-Inception: 01.02.2025, 15:05:35 +, KeyTag 37331, Signer-Name: net






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






Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: ddns.net

ddns.net
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 "e51o1pdujacqu01c7sqi76kt359m7agm" between the hashed NSEC3-owner "e51jqbmja3cp91sa39o2rsf4m91a6ocu" and the hashed NextOwner "e51peeeeaj4k8hqim65ha9l4sei317p8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e51jqbmja3cp91sa39o2rsf4m91a6ocu.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2025, 03:02:56 +, Signature-Inception: 31.01.2025, 01:52:56 +, KeyTag 10024, Signer-Name: net






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "ddns.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 08.02.2025, 03:07:15 +, Signature-Inception: 01.02.2025, 01:57:15 +, KeyTag 10024, Signer-Name: net






0 DNSKEY RR found









Zone: dayfin.ddns.net

dayfin.ddns.net
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.dayfin.ddns.net

www.dayfin.ddns.net
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.dayfin.ddns.net
  nf1.no-ip.com

dayfin.ddns.net
  nf1.no-ip.com / frana1
194.62.182.53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC

ddns.net
  nf1.no-ip.com / frana1
194.62.182.53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


  nf2.no-ip.com / frana2
45.54.64.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2607:f740:e626::53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


  nf3.no-ip.com / frana1
204.16.253.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


  nf4.no-ip.com / frana2
194.62.183.53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1830::53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


  nf5.no-ip.com / frana1
204.16.253.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC

net
  a.gtld-servers.net / nnn1-usiad-1


  b.gtld-servers.net / nnn1-elwaw4


  c.gtld-servers.net / nnn1-usiad-1


  d.gtld-servers.net / nnn1-usiad-1


  e.gtld-servers.net / nnn1-usiad-1


  f.gtld-servers.net / nnn1-defra-4


  g.gtld-servers.net / nnn1-defra-4


  h.gtld-servers.net / nnn1-defra-4


  i.gtld-servers.net / nnn1-defra-4


  j.gtld-servers.net / nnn1-frmrs-2


  k.gtld-servers.net / nnn1-frmrs-2


  l.gtld-servers.net / nnn1-frmrs-2


  m.gtld-servers.net / nnn1-ein4

 

4. SOA-Entries


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


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


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426371
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:3


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426371
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:3


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426376
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:5


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426376
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:5


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426393
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:2


Domain:ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426393
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:2


Domain:dayfin.ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426393
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:1


Domain:dayfin.ddns.net
Zone-Name:ddns.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2616426396
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:1


Domain:www.dayfin.ddns.net
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://dayfin.ddns.net/
136.33.163.240
302
http://dayfin.ddns.net/web/

0.250
D
Date: Mon, 03 Feb 2025 22:05:04 GMT
Server: Kestrel
Location: web/
Content-Length: 0

• http://dayfin.ddns.net/web/
br used - 2128 / 9681 - 78.02 %
200

Html is minified: 120.16 %
0.233
H
Date: Mon, 03 Feb 2025 22:05:05 GMT
Server: Kestrel
Accept-Ranges: bytes
ETag: "1db27cefe4169d1"
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Response-Time-ms: 1.913
Content-Type: text/html
Content-Encoding: br
Last-Modified: Sat, 26 Oct 2024 17:46:32 GMT
Content-Length: 2128

• https://dayfin.ddns.net/
136.33.163.240
-103


0.280
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• http://dayfin.ddns.net:443/
136.33.163.240
302
http://dayfin.ddns.net/web/

0.250
Q
Visible Content:
Date: Mon, 03 Feb 2025 22:05:05 GMT
Server: Kestrel
Location: web/
Content-Length: 0

• http://dayfin.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
136.33.163.240
404


0.144
A
Not Found
Visible Content:
Date: Mon, 03 Feb 2025 22:05:04 GMT
Server: Kestrel
X-Response-Time-ms: 0.0911
Content-Length: 0

• https://136.33.163.240/
136.33.163.240
-103


0.284
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

 

7. Comments


1. General Results, most used to calculate the result

Aname "dayfin.ddns.net" is domain, public suffix is ".ddns.net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 9994 (complete: 263653)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: dayfin.ddns.net has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: dayfin.ddns.net has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood - only one version with Http-Status 200
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.
http://dayfin.ddns.net/web/


Url with incomplete Content-Type - header - missing charset
Dhttp://dayfin.ddns.net/ 136.33.163.240
302
http://dayfin.ddns.net/web/
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
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.
Qhttp://dayfin.ddns.net:443/ 136.33.163.240
302
http://dayfin.ddns.net/web/
Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
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 dayfin.ddns.net, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.dayfin.ddns.net

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.2 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 5 different Name Servers found: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 4 Name Servers included in Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, 5 Name Servers included in 1 Zone definitions: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 1 Name Servers listed in SOA.Primary: nf1.no-ip.com.
AGood: Only one SOA.Primary Name Server found.: nf1.no-ip.com.
AGood: SOA.Primary Name Server included in the delegation set.: nf1.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf1.no-ip.com (194.62.182.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf1.no-ip.com (2a07:dc00:1820::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf2.no-ip.com (45.54.64.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf2.no-ip.com (2607:f740:e626::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf3.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf3.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf4.no-ip.com (194.62.183.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf4.no-ip.com (2a07:dc00:1830::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf5.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf5.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
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: 5 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 5 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.: 5 Name Servers, 1 Top Level Domain: com
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: no-ip.com
Warning: All Name Servers from the same Country / IP location.: 5 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 5 Name Servers, 3 different subnets (first Byte): 194., 204., 45., 3 different subnets (first two Bytes): 194.62., 204.16., 45.54., 4 different subnets (first three Bytes): 194.62.182., 194.62.183., 204.16.253., 45.54.64.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 5 Name Servers with IPv6, 3 different subnets (first block): 2607:, 2620:, 2a07:, 3 different subnets (first two blocks): 2607:f740:, 2620:0000:, 2a07:dc00:, 4 different subnets (first three blocks): 2607:f740:e626:, 2620:0000:2e61:, 2a07:dc00:1820:, 2a07:dc00:1830:, 4 different subnets (first four blocks): 2607:f740:e626:0000:, 2620:0000:2e61:0000:, 2a07:dc00:1820:0000:, 2a07:dc00:1830:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: nf1.no-ip.com: 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.
Nameserver doesn't pass all EDNS-Checks: nf1.no-ip.com / 194.62.182.53: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok (frana1). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: nf3.no-ip.com / 204.16.253.53: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (frana1). COOKIE: ok. CLIENTSUBNET: ok.
XFatal error: Nameservers with different SOA Serial Numbers
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.

4. 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.
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: 95587 milliseconds, 95.587 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" > of the last months 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. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com

 

QNr.DomainTypeNS used
1
com
NS
l.root-servers.net (2001:500:9f::42)

Answer: 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
2
nf1.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
3
nf2.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
4
nf3.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
5
nf4.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
6
nf5.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
7
nf1.no-ip.com: 194.62.182.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
8
nf1.no-ip.com: 2a07:dc00:1820::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
9
nf2.no-ip.com: 45.54.64.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
10
nf2.no-ip.com: 2607:f740:e626::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
11
nf3.no-ip.com: 204.16.253.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
12
nf3.no-ip.com: 2620:0:2e61::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
13
nf4.no-ip.com: 194.62.183.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
14
nf4.no-ip.com: 2a07:dc00:1830::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
15
nf5.no-ip.com: 204.16.253.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
16
nf5.no-ip.com: 2620:0:2e61::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
dayfin.ddns.net
0

no CAA entry found
1
0
ddns.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dayfin.ddns.net

ok
1
0
_acme-challenge.dayfin.ddns.net

Name Error - The domain name does not exist
1
0
_acme-challenge.dayfin.ddns.net.dayfin.ddns.net

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No results

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=5b6795a8-0c43-471c-bcdb-c4741beb3cc7

 

Last Result: https://check-your-website.server-daten.de/?q=dayfin.ddns.net - 2025-02-03 23:03:57

 

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

 

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

 

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=dayfin.ddns.net