iezzi.ch Report : Visit Site


  • Ranking Alexa Global: # 19,401,038

    Server:Apache/2.4...

    The main IP address: 46.231.201.209,Your server Switzerland,Zurich ISP:Metanet AG  TLD:ch CountryCode:CH

    The description :pipo's techblog about linux, security, php, technology and more....

    This report updates in 27-Aug-2018

Technical data of the iezzi.ch


Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host iezzi.ch. Currently, hosted in Switzerland and its service provider is Metanet AG .

Latitude: 47.366668701172
Longitude: 8.5500001907349
Country: Switzerland (CH)
City: Zurich
Region: Zurich
ISP: Metanet AG

the related websites

HTTP Header Analysis


HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4 containing the details of what the browser wants and will accept back from the web server.

Upgrade:h2
Content-Encoding:gzip
Transfer-Encoding:chunked
Accept-Ranges:none
Vary:Accept-Encoding,Cookie
Keep-Alive:timeout=5, max=100
Server:Apache/2.4
Last-Modified:Mon, 27 Aug 2018 15:32:22 GMT
Connection:Upgrade, Keep-Alive
Cache-Control:max-age=3, must-revalidate
Date:Mon, 27 Aug 2018 15:34:48 GMT
X-Frame-Options:SAMEORIGIN
Content-Type:text/html; charset=UTF-8

DNS

soa:ns1.onlime.ch. hostmaster.onlime.ch. 2018082002 3600 900 1814400 180
txt:"v=spf1 include:onlime.ch -all"
ns:ns3.onlime.ch.
ns2.onlime.ch.
ns1.onlime.ch.
ipv4:IP:46.231.201.209
ASN:21069
OWNER:ASN-METANET Routing/peering issues: [email protected], CH
Country:CH
mx:MX preference = 50, mail exchanger = mx2.onlime.ch.
MX preference = 10, mail exchanger = mx1.onlime.ch.

HtmlToText

blog shots about contact me blog shots about contact me just another tech blog about linux, security, tech and stuff blog proxmoxve 4.x openvz to lxc migration sep 4, 2016 posted by iezzip debian linux , technical 0 comments 18 at onlime webhosting we chose proxmoxve as our favorite virtualization platform and are running a bunch of openvz containers for many years now, with almost zero issues. we very much welcome the small overhead and simplicity of container based virtualization and wouldn’t want to move to anything else. proxmoxve added zfs support by integrating zfsonlinux back in feb 2015 with the great proxmoxve 3.4 release – which actually would have deserved to bump its major version because of this killer feature. previously we have been running our openvz containers on plain debian linux boxes. but with debian wheezy (7.0) the debian community decided to no longer include a kernel which has been patched with the openvz extensions. switching to proxmoxve at that time was a piece of cake as proxmoxve was just a plain debian linux with a rhel kernel, openvz and kvm support, and some nice web interface to manage the containers and vms. actually, we never really needed the proxmoxve web interface (guis always suck!), but that one is quite lightweight and very well integrated. if you don’t like it, use the provided cli tools – proxmoxve does not force you to use the web interface at all. in 2014 i did a review for proxmox high availability (by packt publishing) . but at onlime, we never employed any cluster technologies to date. i was always looking for simple solutions without unnecessary complexity. proxmoxve with openvz on zfs pools was the perfect match. we are replicating our containers from one host node to another every 10mins with simple and super fast zfs send|receive via a modified version of zrep . in proxmoxve 4, openvz support was removed in favor of lxc. both, kvm and lxc are built into any newer linux kernel, so in the long term (and due to the nature of openvz as a huge kernel patch which is hard to maintain) it was clear we had to give up openvz. even though the openvz developers are currently focusing on merging the openvz and virtuozzo source codebase and have just released openvz 7.0 i don’t give openvz a long future any more. in comparison to lxc, the tools for openvz are still much more mature and powerful, but lately lxc made a lot of progress and having it perfectly integrated into proxmoxve is a great step forward. so, we have decided to migrate to lxc. (sorry about the long preface. you probably don’t care about history reading this blog post. i am getting to the point now…) what i cannot believe and what prevented me to look into lxc on proxmoxve up to now is the clumsy migration path that proxmoxve suggests on proxmoxve wiki: convert openvz to lxc . basically they suggest to dump and restore a full container as follows: shell pve3$ vzctl stop 100 && vzdump 100 -storage local pve3$ scp /var/lib/vz/dump/vzdump-openvz-100.tar root@pve4:/var/lib/vz/dump/ pve4$ pct restore 100 /var/lib/vz/dump/vzdump-openvz-100.tar 1 2 3 4 5 pve3 $ vzctl stop 100 && vzdump 100 - storage local pve3 $ scp / var / lib / vz / dump / vzdump - openvz - 100.tar root @ pve4 : / var / lib / vz / dump / pve4 $ pct restore 100 / var / lib / vz / dump / vzdump - openvz - 100.tar srsly? do you guys only have containers with sizes below 1gb and don’t care about downtime at all? real world looks different and i would not even go this migration path with a 5gb container. i don’t even want to think about those containers with ~ 1tb of data. if you are running openvz containers on proxmoxve, sure you have some easy solution to migrate your containers from one host node to another. as i said, we are using zrep for container replication and have written a wrapper script that migrates a container to its failover host node. that’s what i suggest and please forget about live migration – it never really was working in openvz (well, it was, but i am talking about a really stable solution that never fails) and lxc lacks any kind of hot/live migration. doing a zrep presync, stopping the container on the source host node, doing the main zrep sync, finally starting the container on the destination host node is just a matter of seconds, usually causes a downtime of 10s up to 30s max (on a larger container). read more setting up php & mysql on os x yosemite okt 20, 2014 posted by iezzip mac os x , php , technical 1 comment 17 homebrew homebrew is a package manager for os x. install it, as we’ll need it later: $ ruby -e "$(curl -fssl https://raw.githubusercontent.com/homebrew/install/master/install)" 1 2 3 $ ruby - e "$(curl -fssl https://raw.githubusercontent.com/homebrew/install/master/install)" you’ll also need the xcode command line tools – at least version 6.1. xcode is available on the mac app store as a free download. don’t forget to start up xcode at least once after initial installation. initially and after every major os x upgrade, you might need to reinstall the xcode command line tools and accept the license aggreement : $ xcode-select --install $ sudo xcodebuild -license 1 2 3 4 $ xcode - select -- install $ sudo xcodebuild - license also, don’t forget to create this missing symlink after upgrading to a new major osx version: $ sudo ln -s /applications/xcode.app/contents/developer/toolchains/xcodedefault.xctoolchain /applications/xcode.app/contents/developer/toolchains/osx10.10.xctoolchain 1 2 3 $ sudo ln - s / applications / xcode . app / contents / developer / toolchains / xcodedefault . xctoolchain / applications / xcode . app / contents / developer / toolchains / osx10 . 10.xctoolchain once homebrew is set up and you want to upgrade outdated packages, run: $ brew update $ brew upgrade 1 2 3 4 $ brew update $ brew upgrade remember to also run brew update && brew upgrade after upgrading to a new major os x version. list all installed packages: $ brew list --versions 1 2 3 $ brew list -- versions you should never be required to run brew as root using sudo ! read more sendmail-wrapper for php mrz 24, 2014 posted by iezzip debian linux , php , security , technical 0 comments 19 years ago i wrote about the extensive sendmail wrapper with sender throttling , a pretty simple perl script. it reliably provided throttling of the email volume per day by the sender’s original uid (user id). it also logged the pathes of scripts that sent emails directly via sendmail (e.g. via php’s mail() function ). the main flaw in the original sendmail wrapper was security, though. as in linux, every executable script must be readable by the user that calls it, the throttle table in mysql was basically open and every customer could manipulate it. every customer could raise his own throttling limit and circumvent it. today, i’m publishing my new sendmail-wrapper that is going to fix all the flaws of the previous version and add some nice extras. the new sendmail-wrapper is written entirely in php and does not require any external libraries. it is a complete rewrite and has pretty much nothing in common with the old perl version. this project is hosted on github https://github.com/onlime/sendmail-wrapper features: lets you monitor any mail traffic from php scripts allows throttling (limiting) emails sent by php’s mail() function throttle by sent email and/or recipient count per day logs both to syslog and database with message metadata logs common mail headers like from, to, cc, bcc, subject fixes return-path header on the fly for users who did not correctly set it highly secured setup , customers cannot access the logging/throttling database standalone php application without any external library dependencies built for shared webhosting environment where php runs as cgi/fastcgi/suphp no cronjobs required , sendmail-wrapper will reset counters automatically every day read more webapp-scanner mrz 24, 2014 posted by iezzip security , technical 0 comments 1

URL analysis for iezzi.ch


https://www.iezzi.ch/webapp-scanner/#more-840
https://www.iezzi.ch/author/iezzip/
https://www.iezzi.ch/extensive-sendmail-wrapper-with-sender-throttling/#comments
https://www.iezzi.ch/tag/homebrew/
https://www.iezzi.ch/tag/nginx/
https://www.iezzi.ch/archives/111
https://www.iezzi.ch/www.php.net/manual/en/function.mail.php
https://www.iezzi.ch/tag/bike-park/
https://www.iezzi.ch/tag/jpeg/
https://www.iezzi.ch/more-os-x-leopard-tips-tricks/
https://www.iezzi.ch/wp-content/uploads/webappscanner.png
https://www.iezzi.ch/proxmoxve-4-x-openvz-to-lxc-migration/#more-948
https://www.iezzi.ch/tag/data-loss-bug/
https://www.iezzi.ch/tag/debian-linux/
https://www.iezzi.ch/fix-snow-leopard-issues-with-smb/#comments

Whois Information


Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

The number of requests per client per time interval is
restricted. You have exceeded this limit.
Please wait a moment and try again.


  REFERRER http://www.nic.ch

  REGISTRAR SWITCH Domain Name Registration

SERVERS

  SERVER ch.whois-servers.net

  ARGS iezzi.ch

  PORT 43

  TYPE domain

  REGISTERED no

DOMAIN

  NAME iezzi.ch

NSERVER

  NS1.ONLIME.CH 80.74.134.40

  NS2.ONLIME.CH 5.148.177.82

  NS3.ONLIME.CH 80.74.134.53

Go to top

Mistakes


The following list shows you to spelling mistakes possible of the internet users for the website searched .

  • www.uiezzi.com
  • www.7iezzi.com
  • www.hiezzi.com
  • www.kiezzi.com
  • www.jiezzi.com
  • www.iiezzi.com
  • www.8iezzi.com
  • www.yiezzi.com
  • www.iezziebc.com
  • www.iezziebc.com
  • www.iezzi3bc.com
  • www.iezziwbc.com
  • www.iezzisbc.com
  • www.iezzi#bc.com
  • www.iezzidbc.com
  • www.iezzifbc.com
  • www.iezzi&bc.com
  • www.iezzirbc.com
  • www.urlw4ebc.com
  • www.iezzi4bc.com
  • www.iezzic.com
  • www.iezzibc.com
  • www.iezzivc.com
  • www.iezzivbc.com
  • www.iezzivc.com
  • www.iezzi c.com
  • www.iezzi bc.com
  • www.iezzi c.com
  • www.iezzigc.com
  • www.iezzigbc.com
  • www.iezzigc.com
  • www.iezzijc.com
  • www.iezzijbc.com
  • www.iezzijc.com
  • www.iezzinc.com
  • www.iezzinbc.com
  • www.iezzinc.com
  • www.iezzihc.com
  • www.iezzihbc.com
  • www.iezzihc.com
  • www.iezzi.com
  • www.iezzic.com
  • www.iezzix.com
  • www.iezzixc.com
  • www.iezzix.com
  • www.iezzif.com
  • www.iezzifc.com
  • www.iezzif.com
  • www.iezziv.com
  • www.iezzivc.com
  • www.iezziv.com
  • www.iezzid.com
  • www.iezzidc.com
  • www.iezzid.com
  • www.iezzicb.com
  • www.iezzicom
  • www.iezzi..com
  • www.iezzi/com
  • www.iezzi/.com
  • www.iezzi./com
  • www.iezzincom
  • www.iezzin.com
  • www.iezzi.ncom
  • www.iezzi;com
  • www.iezzi;.com
  • www.iezzi.;com
  • www.iezzilcom
  • www.iezzil.com
  • www.iezzi.lcom
  • www.iezzi com
  • www.iezzi .com
  • www.iezzi. com
  • www.iezzi,com
  • www.iezzi,.com
  • www.iezzi.,com
  • www.iezzimcom
  • www.iezzim.com
  • www.iezzi.mcom
  • www.iezzi.ccom
  • www.iezzi.om
  • www.iezzi.ccom
  • www.iezzi.xom
  • www.iezzi.xcom
  • www.iezzi.cxom
  • www.iezzi.fom
  • www.iezzi.fcom
  • www.iezzi.cfom
  • www.iezzi.vom
  • www.iezzi.vcom
  • www.iezzi.cvom
  • www.iezzi.dom
  • www.iezzi.dcom
  • www.iezzi.cdom
  • www.iezzic.om
  • www.iezzi.cm
  • www.iezzi.coom
  • www.iezzi.cpm
  • www.iezzi.cpom
  • www.iezzi.copm
  • www.iezzi.cim
  • www.iezzi.ciom
  • www.iezzi.coim
  • www.iezzi.ckm
  • www.iezzi.ckom
  • www.iezzi.cokm
  • www.iezzi.clm
  • www.iezzi.clom
  • www.iezzi.colm
  • www.iezzi.c0m
  • www.iezzi.c0om
  • www.iezzi.co0m
  • www.iezzi.c:m
  • www.iezzi.c:om
  • www.iezzi.co:m
  • www.iezzi.c9m
  • www.iezzi.c9om
  • www.iezzi.co9m
  • www.iezzi.ocm
  • www.iezzi.co
  • iezzi.chm
  • www.iezzi.con
  • www.iezzi.conm
  • iezzi.chn
  • www.iezzi.col
  • www.iezzi.colm
  • iezzi.chl
  • www.iezzi.co
  • www.iezzi.co m
  • iezzi.ch
  • www.iezzi.cok
  • www.iezzi.cokm
  • iezzi.chk
  • www.iezzi.co,
  • www.iezzi.co,m
  • iezzi.ch,
  • www.iezzi.coj
  • www.iezzi.cojm
  • iezzi.chj
  • www.iezzi.cmo
Show All Mistakes Hide All Mistakes