Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
User-agent: * Sitemap: https://0day.work/sitemap.xml Disallow: /ghost/ Disallow: |
Title | Sebastian Neef - |
Description | Just another security Just another security |
Keywords | N/A |
WebSite | 0day.work |
Host IP | 148.251.132.242 |
Location | Germany |
Site | Rank |
US$1,711,345
Last updated: 2023-05-07 12:19:31
0day.work has Semrush global rank of 6,184,789. 0day.work has an estimated worth of US$ 1,711,345, based on its estimated Ads revenue. 0day.work receives approximately 197,463 unique visitors each day. Its web server is located in Germany, with IP address 148.251.132.242. According to SiteAdvisor, 0day.work is safe to visit. |
Purchase/Sale Value | US$1,711,345 |
Daily Ads Revenue | US$1,580 |
Monthly Ads Revenue | US$47,392 |
Yearly Ads Revenue | US$568,693 |
Daily Unique Visitors | 13,165 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
0day.work. | A | 86399 | IP: 148.251.132.242 |
0day.work. | NS | 86400 | NS Record: NS5.101DOMAIN.COM. |
0day.work. | NS | 86400 | NS Record: NS2.101DOMAIN.COM. |
0day.work. | NS | 86400 | NS Record: NS1.101DOMAIN.COM. |
0day.work. | MX | 86400 | MX Record: 1 belinda.uberspace.de. |
0day.work. | TXT | 86400 | TXT Record: v=spf1 mx ~all |
Sebastian Neef - 0day.work Home Contact @0daywork @gehaxelt Impressum Datenschutz Just another security blog Measuring a Tor Hidden Service’s idle Traffic 19 November 2020 research A month ago, I wondered myself how much traffic an idle hidden service would consume just to keep the necessary circuits open. To answer this question, I set up a BalCCon2k20 CTF: Let Me See And Dawsonite Writeups 28 September 2020 writeups Last weekend, I had the time to play the BalCCon2k20 CTF and since there are no writeups for the last two web challenges yet, I decided to change that. Let Credentials hiding in plain sight or how I pwned your http auth 05 July 2020 research In this blog post I will go over the little research project I did about http authentication credentials hiding in plain sight. Idea A few month ago, I was thinking Damn Vulnerable Bash Web Server 27 February 2020 code This won’t be a long blog post, just a little pointer to an A/D CTF challenge that I created last year: A damn |
HTTP/1.1 301 Moved Permanently Server: nginx/1.14.2 Date: Thu, 28 Oct 2021 00:40:45 GMT Content-Type: text/html Content-Length: 185 Connection: keep-alive Location: https://0day.work/ HTTP/2 200 server: nginx/1.14.2 date: Thu, 28 Oct 2021 00:40:46 GMT content-type: text/html; charset=utf-8 content-length: 11011 x-powered-by: Express cache-control: public, max-age=0 etag: W/"2b03-QE/ULdN+BVESwzCj2BwL4Dcw3Ko" vary: Accept-Encoding |
Domain Name: 0DAY.WORK Registry Domain ID: 1968719_MMd1-WORK Updated Date: 2018-12-16T14:23:32Z Creation Date: 2015-11-01T18:32:47Z Registry Expiry Date: 2025-11-01T18:32:47Z Registrar: 101domain GRS Limited Registrar IANA ID: 1011 Registrar Abuse Contact Email: abuse@101domain.com Registrar Abuse Contact Phone: +1.858-295-4626 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registrant State/Province: BE Registrant Country: DE Name Server: ns1.101domain.com. Name Server: ns5.101domain.com. Name Server: ns2.101domain.com. DNSSEC: unsigned >>> Last update of WHOIS database: 2021-09-15T19:20:45Z <<< |