netzgewitter.com Report : Visit Site

Technical data of the netzgewitter.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host netzgewitter.com. Currently, hosted in United States and its service provider is EDIS GmbH .

HTTP Header Analysis

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

DNS

HtmlToText

my god, it's full of code! home blog coming soon… about easy2boot and “\_iso\e2b\grub\e2b.cfg is missing!” 3 posted by norbert on june 19, 2016 – 18:53 filed under linux tagged as easy2boot , linux this post is for steve si regarding the “ e2b.cfg is missing ” error with easy2boot. i have four identical hard drives which have been removed from a qnap nas. i hooked them up on a pc and tried booting into knoppix with e2b in order to access the four drives. this resulted in the above error. easy2boot v1.80 was installed on the usb stick. after pressing enter, an unreadable line appears at the top of the screen (some strange white pixels – see screenshots at the end). booting into knoppix from dvd works. the four drives form a raid 5 volume. once knoppix is booted (from dvd), the raid volume can be attached with mdadm –assemble –scan just fine. just as steve said, the problem has something to do with the hard drives (or their partitions). e2b boots fine from usb after detaching all four sata cables. the pc has four sata ports. i tried connecting them in different order and realized that only one of the four drives is causing this error. i don’t know why only this disk. all four should be the same since they are from the same raid array. the drives were physically labeled 1 to 4 with a felt pen. the drive which causes the problem is called drive 3. sata 0: ok drive 2 - sata 0: black screen drive 3 - sata 0: e2b.cfg is missing drive 3 - sata 1: e2b.cfg is missing drive 3 - sata 2: ok drive 3 - sata 3: ok drive 4 - sata 0: ok drive 4 - sata 1: ok -- update 2016-07-12: the drive has four partitions. in order to make the problem reproducible for others, i created an image of the whole drive. since the drive is really large (1tb) i filled most of the partitions with zeros. except the first 64kb and the raid superblock at the end of each partition. that way, the drive is almost empty and compresses down to about 1mb. i verified that the image with the deleted parts is still causing the error by writing back the image to a different disk. now the other disk is also causing the problem. here is the link to the compressed image: backup.img.bz2 the image can be written back to a physical disk like this: bzip2 -c -d backup.img.bz2 | dd of=/dev/sda bs=64k note: on my first try, i filled all of the partitions except the raid superblocks with zeros. this image did not cause the problem. so on a hunch i left the first 64kb of each partition. so whatever is causing the problem, has to do with some data at the beginning of one ore more partitions. update 2016-07-13: i did some further experiments. firstly, the raid superblock had no influence. the problem persisted even after overwriting them all with zeros. then i removed partitions one by one from the partition table. that lead to the fact that only the third partition caused the problem. the third partition is unfortunately the largest partition with about 930gb. so i created a new disk with a single small partition which contained only the troublesome beginning 64kb of the former third partition. here i found out that the problem goes away when the partition is too small. i don’t know the size limit though. the problem was showing up again, once i set the size if the partition to nearly 1tb again. i was now even able to reproduce the whole thing inside a virtualbox vm. i created a sparse vdi of about 1tb. since it’s almost empty though, it only uses a couple mb on the host machine. once e2b is booted with virtual machine usb boot inside virtualbox, the error message appears. here is a copy of the virtual machine: e2btest_vbox.zip and here are the mbr and the first 64kb of the partition (the drive in the vm already contains a disk with that data): mbr: mbr_v4.bin first 64k of partition: part_start.bin update 2016-08-12: steve reported that the bug in grub4dos has been fixed. and i can confirm, the problem is gone in the latest version of easy2boot hexdump of the first few bytes of each drive drive 3: this is the drive which causes the error : 00000000 fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 |................| 00000010 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 |...|.........!..| 00000020 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 |....8.u........u| 00000030 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74 01 8b |.........|...t..| 00000040 4c 02 cd 13 ea 00 7c 00 00 eb fe 00 00 00 00 00 |l.....|.........| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 5b ba 0e 00 00 00 00 00 |........[.......| 000001c0 29 00 83 fe 3f 41 28 00 00 00 9a 2d 10 00 00 00 |)...?a(....-....| 000001d0 07 42 83 fe 3f 83 c8 2d 10 00 bc 2d 10 00 00 00 |.b..?..-...-....| 000001e0 05 84 83 fe ff ff 88 5b 20 00 ba 8c 40 74 00 fe |.......[ ...@t..| 000001f0 ff ff 83 fe ff ff 48 e8 60 74 b8 32 0f 00 55 aa |......h.`t.2..u.| 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00005000 6d 64 61 64 6d 3a 20 61 64 64 65 64 20 2f 64 65 |mdadm: added /de| 00005010 76 2f 73 64 64 31 0a 00 00 00 00 00 00 00 00 00 |v/sdd1..........| 00005020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00005400 b0 81 00 00 a0 05 02 00 00 00 00 00 f8 88 01 00 |................| 00005410 9f 80 00 00 00 00 00 00 02 00 00 00 02 00 00 00 |................| 00005420 00 80 00 00 00 80 00 00 f0 19 00 00 0a 80 60 57 |..............`w| 00005430 0a 80 60 57 07 00 27 00 53 ef 01 00 01 00 00 00 |..`w..'.s.......| 00005440 49 25 60 57 00 4e ed 00 00 00 00 00 01 00 00 00 |i%`w.n..........| 00005450 00 00 00 00 0b 00 00 00 00 01 00 00 3c 00 00 00 |............<...| 00005460 02 00 00 00 03 00 00 00 49 45 de 80 4d 66 49 95 |........ie..mfi.| 00005470 ac 04 25 bf 75 23 63 e7 00 00 00 00 00 00 00 00 |..%.u#c.........| 00005480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * drive 1: 00000000 fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 |................| 00000010 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 |...|.........!..| 00000020 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 |....8.u........u| 00000030 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74 01 8b |.........|...t..| 00000040 4c 02 cd 13 ea 00 7c 00 00 eb fe 00 00 00 00 00 |l.....|.........| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 1c 9a 08 00 00 00 00 00 |................| 000001c0 29 00 83 fe 3f 41 28 00 00 00 9a 2d 10 00 00 00 |)...?a(....-....| 000001d0 07 42 83 fe 3f 83 c8 2d 10 00 bc 2d 10 00 00 00 |.b..?..-...-....| 000001e0 05 84 83 fe ff ff 88 5b 20 00 ba 8c 40 74 00 fe |.......[ ...@t..| 000001f0 ff ff 83 fe ff ff 48 e8 60 74 b8 32 0f 00 55 aa |......h.`t.2..u.| 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00005000 6d 64 61 64 6d 3a 20 61 64 64 65 64 20 2f 64 65 |mdadm: added /de| 00005010 76 2f 73 64 64 31 0a 00 00 00 00 00 00 00 00 00 |v/sdd1..........| 00005020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00005400 b0 81 00 00 a0 05 02 00 00 00 00 00 f8 88 01 00 |................| 00005410 9f 80 00 00 00 00 00 00 02 00 00 00 02 00 00 00 |................| 00005420 00 80 00 00 00 80 00 00 f0 19 00 00 b7 fb 66 57 |..............fw| 00005430 b7 fb 66 57 0b 00 27 00 53 ef 01 00 01 00 00 00 |..fw..'.s.......| 00005440 49 25 60 57 00 4e ed 00 00 00 00 00 01 00 00 00 |i%`w.n..........| 00005450 00 00 00 00 0b 00 00 00 00 01 00 00 3c 00 00 00 |............<...| 00005460 02 00 00 00 03 00 00 00 49 45 de 80 4d 66 49 95 |........ie..mfi.| 00005470 ac 04 25 bf 75 23 63 e7 00 00 00 00 00 00 00 00 |..%.u#c.........| 00005480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * drive 2: 00000000 fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 |................| 00000010 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 |...|.........!..| 00000020 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 |....8.u........u| 00000030 f3 eb 16 b4 02 b0 01 bb 00

URL analysis for netzgewitter.com

https://www.netzgewitter.com/category/hacking/
https://www.netzgewitter.com/wp-content/uploads/2015/02/great_scott.gif
https://www.netzgewitter.com/2015/05/
https://www.netzgewitter.com/wp-content/uploads/2013/10/custom_kernel.jpg
https://www.netzgewitter.com/tag/hard-drive/
https://www.netzgewitter.com/tag/google/
https://www.netzgewitter.com/coming-soon/
https://www.netzgewitter.com/wp-content/uploads/2016/06/dsc06219_s.jpg
https://www.netzgewitter.com/tag/openssl/
https://www.netzgewitter.com/files/public/part_start.bin
https://www.netzgewitter.com/2015/02/
https://www.netzgewitter.com/category/hardware/raspberry-pi/
https://www.netzgewitter.com/author/norbert/
https://www.netzgewitter.com/category/programming/
https://www.netzgewitter.com/2016/06/

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;

Domain Name: NETZGEWITTER.COM
Registry Domain ID: 1670110143_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2018-06-25T16:56:09Z
Creation Date: 2011-08-02T19:32:46Z
Registry Expiry Date: 2019-08-02T19:32:46Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.REGISTRAR-SERVERS.COM
Name Server: DNS2.REGISTRAR-SERVERS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-01-28T11:29:29Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR NameCheap, Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =netzgewitter.com

  PORT 43

  TYPE domain

DOMAIN

  NAME netzgewitter.com

  CHANGED 2018-06-25

  CREATED 2011-08-02

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS1.REGISTRAR-SERVERS.COM 216.87.155.33

  DNS2.REGISTRAR-SERVERS.COM 216.87.152.33

  REGISTERED yes

Mistakes

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