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




1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
blog.silbernagel.eu
A
185.26.105.244
Lille/Hauts-de-France/France (FR) - Avenir Telematique SAS
Hostname: redirect.netim.net
yes
1
0

AAAA

yes


www.blog.silbernagel.eu

Name Error
yes
1
0
*.silbernagel.eu
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.blog.silbernagel.eu
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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 59479, DigestType 2 and Digest XbqoG8C+/pIYhtjaKEmNn9RBtFf7DjZCoLL5gRyOFeA=



1 RRSIG RR to validate DS RR found



RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2020, 05:00:00 +, Signature-Inception: 01.08.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 50124, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.08.2020, 14:18:46 +, Signature-Inception: 28.07.2020, 13:59:59 +, KeyTag 50124, Signer-Name: eu



RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.08.2020, 14:18:46 +, Signature-Inception: 28.07.2020, 13:59:59 +, KeyTag 59479, Signer-Name: eu



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



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



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

Zone: silbernagel.eu
silbernagel.eu
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 23879, DigestType 2 and Digest oXemT8LsYNgy9qai1X6I9g1Sc6hj9iN/D2fvSy9E6Gw=



1 RRSIG RR to validate DS RR found



RRSIG-Owner silbernagel.eu., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.08.2020, 21:32:48 +, Signature-Inception: 30.07.2020, 20:38:23 +, KeyTag 50124, Signer-Name: eu



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 31534, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner silbernagel.eu., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:15:54 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 23879, Signer-Name: silbernagel.eu



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



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

Zone: blog.silbernagel.eu
blog.silbernagel.eu
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 "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" between the hashed NSEC3-owner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" and the hashed NextOwner "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 185.26.105.244
Validated: RRSIG-Owner blog.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 09.08.2020, 02:11:30 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" equal the hashed NSEC3-owner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" and the hashed NextOwner "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" equal the hashed NSEC3-owner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" and the hashed NextOwner "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" equal the hashed NSEC3-owner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" and the hashed NextOwner "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.blog.silbernagel.eu) sends a valid NSEC3 RR as result with the hashed owner name "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" (unhashed: blog.silbernagel.eu). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ail8ct6cuup3kecudroal703ru9fhadh" (unhashed: _tcp.blog.silbernagel.eu) with the owner "afm2qa5hvdtordpg9a6livivdaf1q150" and the NextOwner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner afm2qa5hvdtordpg9a6livivdaf1q150.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.08.2020, 04:29:09 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "qjr2ks4025g6do8jjmeli2qsod1uurup" (unhashed: *.blog.silbernagel.eu) with the owner "ljo48l1vhlb7v3vc75cu02m5jlh8i444" and the NextOwner "afm2qa5hvdtordpg9a6livivdaf1q150". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.blog.silbernagel.eu) sends a valid NSEC3 RR as result with the owner name "ljo48l1vhlb7v3vc75cu02m5jlh8i444" greater the NextOwner-Name "afm2qa5hvdtordpg9a6livivdaf1q150", so the NSEC3 covers the end of the zone. The hashed query name "mdicfqtpj9b1fd8jaluq3ucg7q3mrg7u" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ljo48l1vhlb7v3vc75cu02m5jlh8i444.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 10:17:56 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" equal the hashed NSEC3-owner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" and the hashed NextOwner "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Status: Good. NoData-Proof required and found.

Zone: www.blog.silbernagel.eu
www.blog.silbernagel.eu
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 "i35j3iiibmmretu3m8aar3p8kt8je14t" between the hashed NSEC3-owner "afm2qa5hvdtordpg9a6livivdaf1q150" and the hashed NextOwner "j2ck9s7b1ccaj4iepc81bkmibb8hgc90". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner afm2qa5hvdtordpg9a6livivdaf1q150.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.08.2020, 04:29:09 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ljo48l1vhlb7v3vc75cu02m5jlh8i444.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 10:17:56 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j2ck9s7b1ccaj4iepc81bkmibb8hgc90" as Owner. That's the Hash of "blog.silbernagel.eu" with the NextHashedOwnerName "ljo48l1vhlb7v3vc75cu02m5jlh8i444". So that domain name is the Closest Encloser of "www.blog.silbernagel.eu". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner j2ck9s7b1ccaj4iepc81bkmibb8hgc90.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 22:12:21 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu



The ClosestEncloser says, that "*.blog.silbernagel.eu" with the Hash "qjr2ks4025g6do8jjmeli2qsod1uurup" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "ljo48l1vhlb7v3vc75cu02m5jlh8i444" and the Next Owner "afm2qa5hvdtordpg9a6livivdaf1q150", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ljo48l1vhlb7v3vc75cu02m5jlh8i444.silbernagel.eu., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.08.2020, 10:17:56 +, Signature-Inception: 09.07.2020, 18:54:35 +, KeyTag 31534, Signer-Name: silbernagel.eu


3. Name Servers

DomainNameserverNS-IP
www.blog.silbernagel.eu
  ns1.netim.net

blog.silbernagel.eu
  ns1.netim.net
198.50.216.33
Beauharnois/Quebec/Canada (CA) - OVH Hosting

silbernagel.eu
  ns1.netim.net
198.50.216.33
Beauharnois/Quebec/Canada (CA) - OVH Hosting


  ns2.netim.net / reg-fra1_customer6
192.174.68.97
Salzburg/Austria (AT) - NICat-anycast


 
2001:67c:1bc::97
Salzburg/Austria (AT) - IPCom-NET Anycast


  ns3.netim.net / reg-ffm1_customer6
176.97.158.97
Vienna/Austria (AT) - NICat-anycast


 
2001:67c:10b8::97
Zurich/Switzerland (CH) - IPCOM-anycast


  ns4.netim.net


  ns5.netim.net

eu
X  nl.dns.eu


  si.dns.eu


  w.dns.eu / tld-eu-fra1


  x.dns.eu / ns-1.eu.de8.bind


  y.dns.eu / s2.amx


4. SOA-Entries


Domain:eu
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124276
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:1


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124276
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:1


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124278
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:2


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124278
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:2


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124293
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:1


Domain:eu
Zone-Name:eu
Primary:nl.dns.eu
Mail:tech.eurid.eu
Serial:1064124293
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:1


Domain:silbernagel.eu
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:silbernagel.eu
Zone-Name:silbernagel.eu
Primary:ns1.netim.net
Mail:hostmaster.netim.net
Serial:2020070929
Refresh:10800
Retry:7200
Expire:604800
TTL:3600
num Entries:5


Domain:blog.silbernagel.eu
Zone-Name:silbernagel.eu
Primary:ns1.netim.net
Mail:hostmaster.netim.net
Serial:2020070929
Refresh:10800
Retry:7200
Expire:604800
TTL:3600
num Entries:1


Domain:www.blog.silbernagel.eu
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://blog.silbernagel.eu/
185.26.105.244 GZip used - 892 / 1483 - 39.85 %
200

Html is minified: 169.49 %
1.067
H
small visible content (num chars: 123)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> mSi &#8211; Das Blog.
Date: Sat, 01 Aug 2020 13:50:42 GMT
Server: Apache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 892
Connection: close
Content-Type: text/html; charset=UTF-8

• https://blog.silbernagel.eu/
185.26.105.244
-14

10.030
T
Timeout - The operation has timed out

• http://blog.silbernagel.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.26.105.244 GZip used - 779 / 1181 - 34.04 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 208.29 %
0.130

Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
Info: Html-Content with frame found, may be a problem creating a Letsencrypt certificate using http-01 validation
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> <html> <head> <title></title> <meta name="Identifier-URL" content="http://blog.silbernagel.eu"> <link rel="SHORTCUT ICON" href="http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/favicon.ico"> </head> <frameset rows="*" frameborder="0" framespacing="0"> <frame src="http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de" name="mainFrameNETIM" > </frameset><noframes></noframes> </html> <!-- server 2 - 185.26.105.246 --> <!-- La page doit faire au minimum 512 octets rhrwfmznc877ctunphny5xvk2brpkrc2f7h155eedpdse6d2r0xyvg56nsyvc6cecjvuyg6pyd104200vhqmsmmkztzd5g7er62pk4pq7pr7g76gyt8hcvg5txb84aqvgsh2x5t3uhaargup916pwpvnj5xpgkhb1176vb0bna244re5x20kxp42juk4bjfcmqjf0ktpxwt0k65f9616v59dzvj9d0p0q7frt8cp35pqcv4n06uwb28aytmau8bgfu771mx5sjv4csd5k8hphum9ey3p8k41uc3d884u29611k6mur9bhwnytrm19s2235gcen5gxcjyyrjseu2zqqxfdhgq8ktcs8r5wxps86p6y6zc00aqr754rpuz8mbv15rzug65dxcb9cck22u76hw0g3nu3fw86v2p02ue5s8h3um6nud4qenu1fygb6q58b6a4m9achvgbepz713yfsrh7p0jvqr20xd5hpfw69bjqhy1nv-->
Date: Sat, 01 Aug 2020 13:50:53 GMT
Server: Apache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 779
Connection: close
Content-Type: text/html; charset=UTF-8

• https://185.26.105.244/
185.26.105.244
-14

10.023
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "blog.silbernagel.eu" is subdomain, public suffix is ".eu", top-level-domain is ".eu", top-level-domain-type is "country-code", Country is European Union, tld-manager is "EURid vzw/asbl", num .eu-domains preloaded: 1407 (complete: 128404)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: blog.silbernagel.eu 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: blog.silbernagel.eu 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://blog.silbernagel.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.26.105.244
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.
XFatal error: Nameserver doesn't support TCP connection: nl.dns.eu: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
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 blog.silbernagel.eu, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 8 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 8 Queries complete, 3 with IPv6, 0 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
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.ns2.netim.net (192.174.68.97, 2001:67c:1bc::97), ns3.netim.net (176.97.158.97, 2001:67c:10b8::97)
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 5 different Name Servers found: ns1.netim.net, ns2.netim.net, ns3.netim.net, ns4.netim.net, ns5.netim.net, 5 Name Servers included in Delegation: ns1.netim.net, ns2.netim.net, ns3.netim.net, ns4.netim.net, ns5.netim.net, 5 Name Servers included in 2 Zone definitions: ns1.netim.net, ns2.netim.net, ns3.netim.net, ns4.netim.net, ns5.netim.net, 1 Name Servers listed in SOA.Primary: ns1.netim.net.
AGood: Only one SOA.Primary Name Server found.: ns1.netim.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.netim.net.
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.netim.net, ns2.netim.net, ns3.netim.net, ns4.netim.net, ns5.netim.net
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 2 Name Servers without ipv4 and ipv6: 2

AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
AGood: Some Name Servers have IPv6 addresses: 2 Name Servers with IPv6 found (1 Name Servers without IPv6)
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.: 3 Name Servers, 1 Top Level Domain: net
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: netim.net
AGood: Name servers with different Country locations found: 3 Name Servers, 3 Countries: AT, CA, CH
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 176., 192., 198., 3 different subnets (first two Bytes): 176.97., 192.174., 198.50., 3 different subnets (first three Bytes): 176.97.158., 192.174.68., 198.50.216.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:01bc:, 2001:067c:10b8:, 2 different subnets (first four blocks): 2001:067c:01bc:0000:, 2001:067c:10b8:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
XNameserver Timeout checking Echo Capitalization: nl.dns.eu
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
XNameserver Timeout checking EDNS512: nl.dns.eu
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: nl.dns.eu: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.netim.net: 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: ns4.netim.net: 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: ns5.netim.net: 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://blog.silbernagel.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.26.105.244
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.
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: 139850 milliseconds, 139.850 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://blog.silbernagel.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.26.105.244
frame

1

1


0
0
0


link
other
1

1


0
0
0


meta
other
1

0


0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
http://blog.silbernagel.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.26.105.244
frame
src
http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


1
http-link, change to https








link
SHORTCUT ICON
http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de/favicon.ico


1
http-link, change to https








meta
Identifier-URL
http://blog.silbernagel.eu


1
ok








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.netim.net, ns2.netim.net, ns3.netim.net

QNr.DomainTypeNS used
1
net
NS
d.root-servers.net (2001:500:2d::d)

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
ns1.netim.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: europe1.dnsnode.net, ns.netim.net, ns2.netim.net, ns3.netim.net, nsp.dnsnode.net

Answer: europe1.dnsnode.net
194.58.196.32, 2a01:3f1:832::53

Answer: ns.netim.net
198.50.216.33

Answer: ns2.netim.net
192.174.68.97, 2001:67c:1bc::97

Answer: ns3.netim.net
176.97.158.97, 2001:67c:10b8::97

Answer: nsp.dnsnode.net
194.58.198.32, 2a01:3f1:3032::53
8
ns1.netim.net: No AAAA record found
AAAA
europe1.dnsnode.net (2a01:3f1:832::53)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
blog.silbernagel.eu
0

no CAA entry found
1
0
silbernagel.eu
0

no CAA entry found
1
0
eu
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
silbernagel.eu

ok
1
0
blog.silbernagel.eu

ok
1
0
_acme-challenge.blog.silbernagel.eu

Name Error - The domain name does not exist
1
0
_acme-challenge.blog.silbernagel.eu.silbernagel.eu

Name Error - The domain name does not exist
1
0
_acme-challenge.blog.silbernagel.eu.blog.silbernagel.eu

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=39f20533-2aeb-482b-a6e0-3a1a2b076518


Last Result: https://check-your-website.server-daten.de/?q=blog.silbernagel.eu - 2020-08-01 15:49:01


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

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