wolfgangziegler.net valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Home | Wolfgang Ziegler //
Description Wolfgang Ziegler // fago Let more not be less. Recursively fixing file permissions Submitted by fago on Sun, 03/01/2015 - 16:22 When you want to recursive
Keywords N/A
Server Information
WebSite wolfgangziegler faviconwolfgangziegler.net
Host IP 76.76.21.21
Location United States
Related Websites
Site Rank
More to Explore
wolfgangziegler.net Valuation
US$391,419
Last updated: 2023-05-11 08:10:18

wolfgangziegler.net has Semrush global rank of 27,040,897. wolfgangziegler.net has an estimated worth of US$ 391,419, based on its estimated Ads revenue. wolfgangziegler.net receives approximately 45,164 unique visitors each day. Its web server is located in United States, with IP address 76.76.21.21. According to SiteAdvisor, wolfgangziegler.net is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$391,419
Daily Ads Revenue US$362
Monthly Ads Revenue US$10,840
Yearly Ads Revenue US$130,072
Daily Unique Visitors 3,011
Note: All traffic and earnings values are estimates.
DNS Records
Host Type TTL Data
wolfgangziegler.net. A 299 IP: 76.76.21.21
wolfgangziegler.net. NS 86400 NS Record: vida.ns.cloudflare.com.
wolfgangziegler.net. NS 86400 NS Record: newt.ns.cloudflare.com.
wolfgangziegler.net. MX 300 MX Record: 1 aspmx.l.google.com.
wolfgangziegler.net. MX 300 MX Record: 10 aspmx3.googlemail.com.
wolfgangziegler.net. MX 300 MX Record: 10 aspmx2.googlemail.com.
wolfgangziegler.net. MX 300 MX Record: 5 alt2.aspmx.l.google.com.
wolfgangziegler.net. MX 300 MX Record: 5 alt1.aspmx.l.google.com.
HtmlToTextCheckTime:2023-05-11 08:10:18
Wolfgang Ziegler // fago Let more not be less. Recursively fixing file permissions Submitted by fago on Sun, 03/01/2015 - 16:22 When you want to recursively fix file permissions, directories usually should get a umask of 755 while files should default to 644 unless they are scripts. Fortunately, chmod has the +X modifier for that: +X only adds the execution bit to directories, while it does not add it to files. It keeps pre-existing execution bits for files though. Thus, to fix all directories to have 755 and files to have 644 or 755 depending on the existing exexcution bit, just run: chmod -R =rwX . If you want to reset all files to 644 also, run chmod -R -x,=rwX . Tags chmod bash Read more about Recursively fixing file permissions 62 comments Auto-rsync local changes to a remote server Submitted by fago on Fri, 04/11/2014 - 18:05 As I’ve never been happy with the performance of Drupal running on behalf nfs shares in vagrant, I’ve been looking into a simple way to rsync my local
HTTP Headers
HTTP/1.1 308 Permanent Redirect
Date: Thu, 04 Nov 2021 09:17:23 GMT
Content-Type: text/plain
Connection: keep-alive
Location: https://wolfgangziegler.net/
Refresh: 0;url=https://wolfgangziegler.net/
server: Vercel
x-vercel-id: cle1::jrz9k-1636017443094-0daea31b2190

HTTP/2 200 
date: Thu, 04 Nov 2021 09:17:23 GMT
content-type: text/html; charset=utf-8
content-length: 48913
content-disposition: inline; filename="index.html"
cache-control: public, max-age=0, must-revalidate
etag: W/"1ed52bd195291b441c29a000e784cdb8c5318701"
access-control-allow-origin: *
age: 3782727
x-vercel-cache: HIT
server: Vercel
x-vercel-id: cle1:cle1::k7n4h-1636017443226-8c2f58362d8a
strict-transport-security: max-age=63072000
accept-ranges: bytes
wolfgangziegler.net Whois Information
Domain Name: WOLFGANGZIEGLER.NET
Registry Domain ID: 1627731971_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.domrobot.com
Registrar URL: http://www.inwx.com
Updated Date: 2020-11-23T08:15:40Z
Creation Date: 2010-11-28T20:13:41Z
Registry Expiry Date: 2022-11-28T20:13:41Z
Registrar: INWX GmbH & Co. KG
Registrar IANA ID: 1420
Registrar Abuse Contact Email: abuse@inwx.com
Registrar Abuse Contact Phone: +49.30983212123
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NEWT.NS.CLOUDFLARE.COM
Name Server: VIDA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
>>> Last update of whois database: 2021-10-22T06:25:38Z <<<