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



X

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

Checked:
22.09.2022 16:02:21


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jabbott.sytes.net
A
31.126.3.58
Martlesham/England/United Kingdom (GB) - British Telecommunications PLC
Hostname: host31-126-3-58.range31-126.btcentralplus.com
yes
1
0

AAAA

yes


www.jabbott.sytes.net

Name Error
yes
1
0
*.jabbott.sytes.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 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: net
net
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.10.2022, 04:00:00 +, Signature-Inception: 22.09.2022, 03: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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 4403, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 16:28:30 +, Signature-Inception: 21.09.2022, 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: sytes.net
sytes.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 "eqcsgb5vluih9bes6vscu3ifn2q7lhfc" between the hashed NSEC3-owner "eqcqebgi43p8hgn37ts4oi2kpmj23mh4" and the hashed NextOwner "eqcso7ob8p6pjo7u72jcjoatcql2nb5q". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner eqcqebgi43p8hgn37ts4oi2kpmj23mh4.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2022, 06:22:24 +, Signature-Inception: 21.09.2022, 05:12:24 +, KeyTag 4403, 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 "sytes.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2022, 06:22:24 +, Signature-Inception: 21.09.2022, 05:12:24 +, KeyTag 4403, Signer-Name: net



0 DNSKEY RR found




Zone: jabbott.sytes.net
jabbott.sytes.net
0 DS RR in the parent zone found



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.jabbott.sytes.net
  nf1.no-ip.com

jabbott.sytes.net
  nf1.no-ip.com / f0202.fra.hv.as29997.net
194.62.182.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC

sytes.net
  nf1.no-ip.com / f0202.fra.hv.as29997.net
194.62.182.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC


  nf2.no-ip.com / f0201.fra.hv.as29997.net
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 / f0201.sin.vr.as29997.net
204.16.253.53
Rio de Janeiro/Brazil (BR) - Vitalwerks Internet Solutions, LLC


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


  nf4.no-ip.com / localhost
194.62.183.53
Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1830::53
Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC


T  nf5.no-ip.com / f0201.sin.vr.as29997.net
204.16.253.53
Rio de Janeiro/Brazil (BR) - Vitalwerks Internet Solutions, LLC


T 
2620:0:2e61::53
Chicago/Illinois/United States (US) - Vitalwerks Internet Solutions, LLC

net
  a.gtld-servers.net / nnn1-par6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-nyc6


  k.gtld-servers.net / nnn1-nyc6


  l.gtld-servers.net / nnn1-nyc6


  m.gtld-servers.net / nnn1-nyc6


4. SOA-Entries


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


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


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384792
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:6


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384792
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:6


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384793
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:2


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384793
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:2


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384795
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:2


Domain:sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384795
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:2


Domain:jabbott.sytes.net
Zone-Name:sytes.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2095384796
Refresh:600
Retry:300
Expire:604800
TTL:600
num Entries:2


Domain:www.jabbott.sytes.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://jabbott.sytes.net/
31.126.3.58 GZip used - 21492 / 65288 - 67.08 %
200

Html is minified: 101.56 %
0.167
H
Server: nginx/1.14.2
Date: Thu, 22 Sep 2022 14:04:09 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://jabbott.sytes.net/
31.126.3.58
-2

1.120
V
ConnectFailure - Unable to connect to the remote server

• http://jabbott.sytes.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
31.126.3.58 GZip used - 132 / 169 - 21.89 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.03 %
0.100
A
Not Found
Visible Content: 404 Not Found nginx/1.14.2
Server: nginx/1.14.2
Date: Thu, 22 Sep 2022 14:04:11 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://31.126.3.58/
31.126.3.58
-2

1.107
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "jabbott.sytes.net" is domain, public suffix is ".sytes.net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 7665 (complete: 199710)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: jabbott.sytes.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: jabbott.sytes.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.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
http://jabbott.sytes.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 31.126.3.58


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.
Vhttps://jabbott.sytes.net/ 31.126.3.58
-2

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

Connect failure - perhaps firewall
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 jabbott.sytes.net, 1 ip addresses.

2. 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
AGood: Name servers with different Country locations found: 5 Name Servers, 3 Countries: BR, NL, 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
XNameserver Timeout checking EDNS512: nf5.no-ip.com / 204.16.253.53
XNameserver Timeout checking EDNS512: nf5.no-ip.com / 2620:0:2e61::53
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 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.
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.
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: 123413 milliseconds, 123.413 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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7595652401
precert
CN=R3, O=Let's Encrypt, C=US
2022-09-22 10:42:28
2022-12-21 11:42:27
jabbott.sytes.net
1 entries


7595501675
precert
CN=R3, O=Let's Encrypt, C=US
2022-09-22 10:11:29
2022-12-21 11:11:28
brewery.sytes.net, izzy.sytes.net, jabbott.sytes.net
3 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: 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
j.root-servers.net (2001:503:c27::2:30)

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)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
jabbott.sytes.net
0

no CAA entry found
1
0
sytes.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jabbott.sytes.net

ok
1
0
_acme-challenge.jabbott.sytes.net

Name Error - The domain name does not exist
1
0
_acme-challenge.jabbott.sytes.net.jabbott.sytes.net

Name Error - The domain name does not exist
1
0


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

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
jabbott.sytes.net
31.126.3.58
21
FTP



jabbott.sytes.net
31.126.3.58
21
FTP



jabbott.sytes.net
31.126.3.58
22
SSH
open
SSH-2.0-OpenSSH_7.9p1 Raspbian-10+deb10u2

jabbott.sytes.net
31.126.3.58
22
SSH
open
SSH-2.0-OpenSSH_7.9p1 Raspbian-10+deb10u2

jabbott.sytes.net
31.126.3.58
25
SMTP



jabbott.sytes.net
31.126.3.58
25
SMTP



jabbott.sytes.net
31.126.3.58
53
DNS



jabbott.sytes.net
31.126.3.58
53
DNS



jabbott.sytes.net
31.126.3.58
110
POP3



jabbott.sytes.net
31.126.3.58
110
POP3



jabbott.sytes.net
31.126.3.58
143
IMAP



jabbott.sytes.net
31.126.3.58
143
IMAP



jabbott.sytes.net
31.126.3.58
465
SMTP (encrypted)



jabbott.sytes.net
31.126.3.58
465
SMTP (encrypted)



jabbott.sytes.net
31.126.3.58
587
SMTP (encrypted, submission)



jabbott.sytes.net
31.126.3.58
587
SMTP (encrypted, submission)



jabbott.sytes.net
31.126.3.58
993
IMAP (encrypted)



jabbott.sytes.net
31.126.3.58
993
IMAP (encrypted)



jabbott.sytes.net
31.126.3.58
995
POP3 (encrypted)



jabbott.sytes.net
31.126.3.58
995
POP3 (encrypted)



jabbott.sytes.net
31.126.3.58
1433
MS SQL



jabbott.sytes.net
31.126.3.58
1433
MS SQL



jabbott.sytes.net
31.126.3.58
2082
cPanel (http)



jabbott.sytes.net
31.126.3.58
2082
cPanel (http)



jabbott.sytes.net
31.126.3.58
2083
cPanel (https)



jabbott.sytes.net
31.126.3.58
2083
cPanel (https)



jabbott.sytes.net
31.126.3.58
2086
WHM (http)



jabbott.sytes.net
31.126.3.58
2086
WHM (http)



jabbott.sytes.net
31.126.3.58
2087
WHM (https)



jabbott.sytes.net
31.126.3.58
2087
WHM (https)



jabbott.sytes.net
31.126.3.58
2089
cPanel Licensing



jabbott.sytes.net
31.126.3.58
2089
cPanel Licensing



jabbott.sytes.net
31.126.3.58
2095
cPanel Webmail (http)



jabbott.sytes.net
31.126.3.58
2095
cPanel Webmail (http)



jabbott.sytes.net
31.126.3.58
2096
cPanel Webmail (https)



jabbott.sytes.net
31.126.3.58
2096
cPanel Webmail (https)



jabbott.sytes.net
31.126.3.58
2222
DirectAdmin (http)



jabbott.sytes.net
31.126.3.58
2222
DirectAdmin (http)



jabbott.sytes.net
31.126.3.58
2222
DirectAdmin (https)



jabbott.sytes.net
31.126.3.58
2222
DirectAdmin (https)



jabbott.sytes.net
31.126.3.58
3306
mySql



jabbott.sytes.net
31.126.3.58
3306
mySql



jabbott.sytes.net
31.126.3.58
5224
Plesk Licensing



jabbott.sytes.net
31.126.3.58
5224
Plesk Licensing



jabbott.sytes.net
31.126.3.58
5432
PostgreSQL



jabbott.sytes.net
31.126.3.58
5432
PostgreSQL



jabbott.sytes.net
31.126.3.58
8080
Ookla Speedtest (http)



jabbott.sytes.net
31.126.3.58
8080
Ookla Speedtest (http)



jabbott.sytes.net
31.126.3.58
8080
Ookla Speedtest (https)



jabbott.sytes.net
31.126.3.58
8080
Ookla Speedtest (https)



jabbott.sytes.net
31.126.3.58
8083
VestaCP http



jabbott.sytes.net
31.126.3.58
8083
VestaCP http



jabbott.sytes.net
31.126.3.58
8083
VestaCP https



jabbott.sytes.net
31.126.3.58
8083
VestaCP https



jabbott.sytes.net
31.126.3.58
8443
Plesk Administration (https)



jabbott.sytes.net
31.126.3.58
8443
Plesk Administration (https)



jabbott.sytes.net
31.126.3.58
8447
Plesk Installer + Updates



jabbott.sytes.net
31.126.3.58
8447
Plesk Installer + Updates



jabbott.sytes.net
31.126.3.58
8880
Plesk Administration (http)



jabbott.sytes.net
31.126.3.58
8880
Plesk Administration (http)



jabbott.sytes.net
31.126.3.58
10000
Webmin (http)



jabbott.sytes.net
31.126.3.58
10000
Webmin (http)



jabbott.sytes.net
31.126.3.58
10000
Webmin (https)



jabbott.sytes.net
31.126.3.58
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=9d9d32b7-d99a-4964-8f66-eaa5db011445


Last Result: https://check-your-website.server-daten.de/?q=jabbott.sytes.net - 2022-09-22 16:02:21


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

<a href="https://check-your-website.server-daten.de/?q=jabbott.sytes.net" target="_blank">Check this Site: jabbott.sytes.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