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



X

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

Checked:
04.05.2021 08:21:09


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
vatukka.servebeer.com
A
91.158.56.80
Joensuu/North Karelia/Finland (FI) - Elisa Oyj
Hostname: 91-158-56-80.elisa-laajakaista.fi
yes
1
0

AAAA

yes


www.vatukka.servebeer.com

Name Error
yes
1
0
*.vatukka.servebeer.com
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14631, Flags 256



Public Key with Algorithm 8, KeyTag 20326, 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: 22.05.2021, 00:00:00 +, Signature-Inception: 01.05.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



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



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

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.05.2021, 20:00:00 +, Signature-Inception: 03.05.2021, 19:00:00 +, KeyTag 14631, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 54714, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.05.2021, 18:24:21 +, Signature-Inception: 30.04.2021, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

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



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "6ifn7ek5ss05uda4un789k85esim7pfi" between the hashed NSEC3-owner "6ifn6jmirga447ejq2p8is7jvq5oeo9d" and the hashed NextOwner "6ifng97skl14l0l8apc46rjcrkujn6ud". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 6ifn6jmirga447ejq2p8is7jvq5oeo9d.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.05.2021, 05:13:21 +, Signature-Inception: 01.05.2021, 04:03:21 +, KeyTag 54714, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "servebeer.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.05.2021, 04:23:37 +, Signature-Inception: 01.05.2021, 03:13:37 +, KeyTag 54714, Signer-Name: com



0 DNSKEY RR found




Zone: vatukka.servebeer.com
vatukka.servebeer.com
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.vatukka.servebeer.com
www.vatukka.servebeer.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.vatukka.servebeer.com
  nf1.no-ip.com

vatukka.servebeer.com
  nf1.no-ip.com / f0202.ams.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

servebeer.com
  nf1.no-ip.com / f0202.ams.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.ams.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.ams.vr.as29997.net
204.16.253.53
Chicago/Illinois/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Piscataway/New Jersey/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


  nf5.no-ip.com / f0202.ams.vr.as29997.net
204.16.253.53
Chicago/Illinois/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Piscataway/New Jersey/United States (US) - Vitalwerks Internet Solutions, LLC

com
  a.gtld-servers.net / nnn1-fra8


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra8


  d.gtld-servers.net / nnn1-fra8


  e.gtld-servers.net / nnn1-fra8


  f.gtld-servers.net / nnn1-ams6


  g.gtld-servers.net / nnn1-ams6


  h.gtld-servers.net / nnn1-ams6


  i.gtld-servers.net / nnn1-ams6


  j.gtld-servers.net / nnn1-ein3


  k.gtld-servers.net / nnn1-ein3


  l.gtld-servers.net / nnn1-ein1


  m.gtld-servers.net / nnn1-ein2


4. SOA-Entries


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


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


Domain:servebeer.com
Zone-Name:servebeer.com
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2018121763
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:8


Domain:servebeer.com
Zone-Name:servebeer.com
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2018121764
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:2


Domain:vatukka.servebeer.com
Zone-Name:servebeer.com
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2018121764
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:2


Domain:www.vatukka.servebeer.com
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://vatukka.servebeer.com/
91.158.56.80 No GZip used - 1925 / 3754 - 51.28 % possible
200

Html is minified: 206.83 %
0.183
H
small visible content (num chars: 161)
Open Source Ad Blocker Designed for Raspberry Pi vatukka.servebeer.com 1 5 [π]: Tuesday 6:21 AM, May 04th. Pi-hole v5.3.1-0-g4736e03 (ubuntu-server/91.158.56.80)
X-Pi-hole: A black hole for Internet advertisements.
Content-type: text/html; charset=UTF-8
Expires: Tue, 04 May 2021 06:21:52 GMT
Cache-Control: max-age=0
Content-Length: 3754
Connection: close
Date: Tue, 04 May 2021 06:21:52 GMT
Server: lighttpd/1.4.55

• https://vatukka.servebeer.com/
91.158.56.80
-2

1.160
V
ConnectFailure - Unable to connect to the remote server

• http://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.158.56.80 No GZip used - 1925 / 3754 - 51.28 % possible
Inline-JavaScript (∑/total): 3/1447 Inline-CSS (∑/total): 0/0
200

Html is minified: 206.83 %
0.170

Visible Content: Open Source Ad Blocker Designed for Raspberry Pi vatukka.servebeer.com 1 5 [π]: Tuesday 6:21 AM, May 04th. Pi-hole v5.3.1-0-g4736e03 (ubuntu-server/91.158.56.80)
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
X-Pi-hole: A black hole for Internet advertisements.
Content-type: text/html; charset=UTF-8
Expires: Tue, 04 May 2021 06:21:54 GMT
Cache-Control: max-age=0
Content-Length: 3754
Connection: close
Date: Tue, 04 May 2021 06:21:54 GMT
Server: lighttpd/1.4.55

• https://91.158.56.80/
91.158.56.80
-2

1.153
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "vatukka.servebeer.com" is domain, public suffix is ".servebeer.com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 57967 (complete: 151507)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: vatukka.servebeer.com 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: vatukka.servebeer.com 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct 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.
Ihttp://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.158.56.80
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Vhttps://vatukka.servebeer.com/ 91.158.56.80
-2

connect failure - perhaps firewall
Vhttps://91.158.56.80/ 91.158.56.80
-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 vatukka.servebeer.com, 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.: 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.: 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.: 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.: 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.: 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.: 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.: 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.: 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.: 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.: 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, 2 Countries: 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
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

http://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.158.56.80
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.158.56.80
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 68150 milliseconds, 68.150 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

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
http://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.158.56.80
a

3

1
1
1
0
0
0


form

1

0


0
0
0


link
stylesheet
1

1
1
0
0
0
0


link
other
1

1
1
0
0
0
0


meta
other
4

0


0
0
0


script

1

1
1
0
0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
http://vatukka.servebeer.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.158.56.80
a

/
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








a

about:home


1
ok








a

https://docs.pi-hole.net/
200

1
ok
, missing X-Content-Type-Options nosniff

9886 Bytes






form




1
ok








link
shortcut icon
admin/img/favicons/favicon.ico
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








link
stylesheet
pihole/blockingpage.css
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








meta

utf-8


1
ok








meta
x-dns-prefetch-control
off


1
ok








meta
robots
noindex,nofollow


1
ok








meta
viewport
width=device-width, initial-scale=1


1
ok








script
src
admin/scripts/vendor/jquery.min.js
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server
Missing defer / async attribute.








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
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)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
vatukka.servebeer.com
0

no CAA entry found
1
0
servebeer.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vatukka.servebeer.com

ok
1
0
_acme-challenge.vatukka.servebeer.com

Name Error - The domain name does not exist
1
0
_acme-challenge.vatukka.servebeer.com.vatukka.servebeer.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=1df85dbe-e8df-4234-954a-4d5262f24cb6


Last Result: https://check-your-website.server-daten.de/?q=vatukka.servebeer.com - 2021-05-04 08:21:09


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

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