Websites herunterladen, die Monkey HTTP Server nutzen
Derzeit nutzen 17 aktive Websites Monkey HTTP Server
Web servers · seit 2001 · open source
Vorschau der Datensätze zu Sites mit Monkey HTTP Server
Die Erkennung von Monkey HTTP Server ist ein Wert in der Spalte Technologies . Zwei Datensätze enthalten sie. Wechseln Sie zwischen beiden, um den Inhalt zu vergleichen.
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000ps-web.de | de | de | ICANN | HTTP 404 | 213.239.212.55 | DE | — | 2026-09-24 | Monkey HTTP Server | 0.00000000914271 | 10,451,909 | — | — |
| antisol.org | org | org | ICANN | HTTP 200 | 139.162.117.133 | JP | — | 2026-09-27 | Monkey HTTP Server | 0.0000000089435 | 12,637,494 | 2011-10-04 | 2027-10-04 |
| casaapatrida.com.py | com.py | py | ICANN | HTTP 403 | 65.21.10.235 | FI | — | 2026-09-30 | Monkey HTTP Server, Google Site Verification | 0.00000000710577 | 12,067,102 | — | — |
| unfall.ru | ru | ru | ICANN | HTTP 200 | 89.108.108.78 | RU | — | 2026-09-21 | PWA, Ruby, Nginx, UIKit, REG.RU, Favicon, Ruby on Rails, Monkey HTTP Server | 0.00000000582858 | 12,723,133 | 2013-03-06 | 2027-03-06 |
| antisol.info | info | info | ICANN | HTTP 200 | 139.162.117.133 | JP | — | 2026-09-27 | Monkey HTTP Server | 0.00000000397692 | 9,686,718 | 2011-10-04 | 2027-10-04 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | DNS last data checked | DNS Status | DNS records | PR value | Harmonic value | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record | Response Status RDAP/WHOIS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000ps-web.de | de | de | ICANN | HTTP 404 | 213.239.212.55 | DE | — | 2026-09-24 | Monkey HTTP Server | 2026-10-01 | TRUE | {"A":["213.239.212.55"],"MX":[{"host":"smx00.udag.de","priority":10},{"host":"smx01.udag.de","priority":10}],"NS":["ns.udag.de","ns.udag.net","ns.udag.org"],"SOA":{"mname":"ns.udag.net","retry":3600,"rname":"hostmaster.united-domains.de","expire":604800,"serial":2023112905,"minimum":3600,"refresh":10800}} | 0.00000000914271 | 10,451,909 | — | — | — | — | — | — | — | — |
| antisol.org | org | org | ICANN | HTTP 200 | 139.162.117.133 | JP | — | 2026-09-27 | Monkey HTTP Server | 2026-09-23 | TRUE | {"A":["139.162.117.133"],"MX":[{"host":"mail.antisol.org","priority":10}],"NS":["dns1.registrar-servers.com","dns2.registrar-servers.com"],"SOA":{"mname":"dns1.registrar-servers.com","retry":3600,"rname":"hostmaster.registrar-servers.com","expire":604800,"serial":1782820658,"minimum":3601,"refresh":43200},"TXT":["v=spf1 mx ip4:139.162.117.133 mx:mail.antisol.org ip6:2400:8902:e001:416:d00f:d00f:d00f:d00f -all"],"AAAA":["2400:8902:e001:416:d00f:d00f:d00f:d00f"]} | 0.0000000089435 | 12,637,494 | 2026-10-03 | RDAP | 2011-10-04 | 2027-10-04 | 2026-09-09 | NameCheap, Inc. | {"raw_response":{"links":[{"rel":"related","href":"https://rdap.namecheap.com/domain/antisol.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org"},{"rel":"self","href":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org"}],"events":[{"eventDate":"2027-10-04T01:21:08.697Z","eventAction":"expiration"},{"eventDate":"2011-10-04T01:21:08.697Z","eventAction":"registration"},{"eventDate":"2026-09-09T06:01:27.047Z","eventAction":"last changed"},{"eventDate":"2026-10-02T22:34:43.045Z","eventAction":"last update of RDAP database"}],"status":["client transfer prohibited"],"ldhName":"antisol.org","notices":[{"links":[{"rel":"terms-of-service","href":"https://thenew.org/org-people/about-pir/policies/","type":"text/html","value":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org"}],"title":"Terms of Service","description":["Public Interest Registry provides this RDAP service for informational purposes only, and to assist persons in obtaining information about or related to a domain name registration record. Public Interest Registry does not guarantee its accuracy. Users accessing the Public Interest Registry RDAP service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Public Interest Registry or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Public Interest Registry RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request to WHOISrequest@pir.org. Public Interest Registry Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."]},{"links":[{"rel":"glossary","href":"https://icann.org/epp","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org"}],"title":"Status Codes","description":["For more information on domain status codes, please visit https://icann.org/epp"]},{"links":[{"rel":"help","href":"https://icann.org/wicf","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/antisol.org"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"self","href":"https://rdap.publicinterestregistry.org/rdap/entity/1068","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/entity/1068"},{"rel":"about","href":"https://rdap.namecheap.com/","type":"application/rdap+json","value":"https://rdap.namecheap.com/"}],"roles":["registrar"],"handle":"1068","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.9854014545"],["email",{},"text","abuse@namecheap.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"1068"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","NameCheap, Inc."]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"47227f63bb3c48848e8be7fa40d579ca-LROR","status":["associated"],"ldhName":"dns1.registrar-servers.com","unicodeName":"dns1.registrar-servers.com","objectClassName":"nameserver"},{"handle":"83d58eee402c4031a15feca6d902c5f1-LROR","status":["associated"],"ldhName":"dns2.registrar-servers.com","unicodeName":"dns2.registrar-servers.com","objectClassName":"nameserver"}],"unicodeName":"antisol.org","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}} | Domain is active |
| casaapatrida.com.py | com.py | py | ICANN | HTTP 403 | 65.21.10.235 | FI | — | 2026-09-30 | Monkey HTTP Server, Google Site Verification | 2026-09-21 | TRUE | {"A":["65.21.10.235"],"NS":["ns1.loszona.com","ns2.loszona.com","ns3.loszona.com"],"CAA":[{"tag":"issue","flags":128,"value":"letsencrypt.org"}],"SOA":{"mname":"ns1.loszona.com","retry":3600,"rname":"dnscontrol.glr.com","expire":604800,"serial":1769509979,"minimum":86400,"refresh":10800},"TXT":["google-site-verification=dPl90sFVpQXfbaELCb4LsQIPMrmzReI4ENjN30d0LTs","v=spf1 -all"],"AAAA":["2a01:4f9:3080:4160::2"]} | 0.00000000710577 | 12,067,102 | — | — | — | — | — | — | — | — |
| unfall.ru | ru | ru | ICANN | HTTP 200 | 89.108.108.78 | RU | — | 2026-09-21 | PWA, Ruby, Nginx, UIKit, REG.RU, Favicon, Ruby on Rails, Monkey HTTP Server | 2026-09-29 | TRUE | {"A":["89.108.108.78"],"NS":["ns1.reg.ru","ns2.reg.ru"],"SOA":{"mname":"ns1.reg.ru","retry":3600,"rname":"hostmaster.ns1.reg.ru","expire":604800,"serial":1771211933,"minimum":10800,"refresh":14400}} | 0.00000000582858 | 12,723,133 | 2026-02-05 | WHOIS | 2013-03-06 | 2027-03-06 | 2026-02-04 | REGRU-RU | {"raw_response":"% TCI Whois Service. Terms of use:\n% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)\n% https://tcinet.ru/documents/whois_su.pdf (in Russian)\n\ndomain: UNFALL.RU\nnserver: ns1.reg.ru.\nnserver: ns2.reg.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\nperson: Private Person\nregistrar: REGRU-RU\nadmin-contact: http://www.reg.ru/whois/admin_contact\ncreated: 2013-03-06T15:37:00Z\npaid-till: 2027-03-06T16:37:00Z\nfree-date: 2027-04-06\nsource: TCI\n\nLast updated on 2026-02-04T23:53:01Z\n\n"} | Domain is active |
| antisol.info | info | info | ICANN | HTTP 200 | 139.162.117.133 | JP | — | 2026-09-27 | Monkey HTTP Server | 2026-10-01 | TRUE | {"A":["139.162.117.133"],"MX":[{"host":"mail.antisol.info","priority":10}],"NS":["dns1.registrar-servers.com","dns2.registrar-servers.com"],"SOA":{"mname":"dns1.registrar-servers.com","retry":3600,"rname":"hostmaster.registrar-servers.com","expire":604800,"serial":1573425890,"minimum":3601,"refresh":43200}} | 0.00000000397692 | 9,686,718 | 2026-10-03 | RDAP | 2011-10-04 | 2027-10-04 | 2026-09-09 | NameCheap, Inc. | {"raw_response":{"links":[{"rel":"related","href":"https://rdap.namecheap.com/domain/antisol.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/antisol.info"},{"rel":"self","href":"https://rdap.identitydigital.services/rdap/domain/antisol.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/antisol.info"}],"events":[{"eventDate":"2027-10-04T01:21:19.876Z","eventAction":"expiration"},{"eventDate":"2011-10-04T01:21:19.876Z","eventAction":"registration"},{"eventDate":"2026-09-09T06:01:45.42Z","eventAction":"last changed"},{"eventDate":"2026-10-02T22:34:47.694Z","eventAction":"last update of RDAP database"}],"status":["active"],"ldhName":"antisol.info","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.identity.digital/policies/rdds-access-policy","type":"text/html","value":"https://rdap.identitydigital.services/rdap/domain/antisol.info"}],"title":"Terms of Service","description":["Access to RDAP information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or, if the record pertains to a TLD not operated by Identity Digital, then the corresponding primary Registry Operator for informational purposes only, and neither Identity Digital nor the Registry Operator guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Identity Digital, a Registrar, or Registry Operator except as reasonably necessary to register domain names or modify existing registrations. When using the RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to the data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/ Identity Digital Inc. and, if applicable, the primary Registry Operators reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."]},{"links":[{"rel":"glossary","href":"https://icann.org/epp","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/antisol.info"}],"title":"Status Codes","description":["For more information on domain status codes, please visit https://icann.org/epp"]},{"links":[{"rel":"help","href":"https://icann.org/wicf","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/antisol.info"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"self","href":"https://rdap.identitydigital.services/rdap/entity/1068","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/entity/1068"},{"rel":"about","href":"https://rdap.namecheap.com/","type":"application/rdap+json","value":"https://rdap.namecheap.com/"}],"roles":["registrar"],"handle":"1068","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.9854014545"],["email",{},"text","abuse@namecheap.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"1068"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","NameCheap, Inc."]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"a14ea728df9944b99008affc2709e0fa-DONUTS","status":["associated"],"ldhName":"dns1.registrar-servers.com","unicodeName":"dns1.registrar-servers.com","objectClassName":"nameserver"},{"handle":"b64adf70a79541e2b681cc4df98578c2-DONUTS","status":["associated"],"ldhName":"dns2.registrar-servers.com","unicodeName":"dns2.registrar-servers.com","objectClassName":"nameserver"}],"unicodeName":"antisol.info","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
Versionsverteilung
Erkannte Versionen von Monkey HTTP Server über alle 17 Sites hinweg.
| Version | Sites | Anteil |
|---|---|---|
| 1.6.8 | 1 | 100.0% |
Der Datensatz Monkey HTTP Server
Jede Site, auf der wir Monkey HTTP Server erkannt haben, mit Version, Hosting, Land, TLD und Traffic-Rang.
Monkey HTTP Server steckt in 2 Datensätzen
Die Erkennung von Monkey HTTP Server ist Teil von Technologies (€159/Mon.) und All data (€599/Mon.). Kaufen Sie einen der beiden, um die vollständige Liste mit 17 Sites zu filtern, oder holen Sie sich zuerst eine kostenlose Vorschau.
Über Monkey HTTP Server
Bei Serversoftware gibt es normalerweise einen Long Tail älterer Versionen, weil jeder Betreiber nach seinem eigenen Zeitplan aktualisiert und alte Builds jahrelang weiterlaufen. Eine so geringe Streuung der Versionen deutet dagegen auf Installationen hin, die einmal als Teil von etwas anderem mitgeliefert und nie wieder angefasst wurden. Am häufigsten sehen wir Version 1.6.8.
Das Produkt ist in C geschrieben, steht unter der Lizenz Apache 2.0 und stammt aus dem Jahr 2001, womit es älter ist als vieles andere in der Kategorie Web servers. Kompakte Server in C gibt es, weil ein Allzweckserver nicht überall hineinpasst. Appliances, Router, Kiosksysteme, Industriesteuerungen und alles andere, bei dem Speicher in Megabyte gezählt wird und sich nie ein Administrator anmelden wird, brauchen trotzdem eine HTTP-Schnittstelle, und gebaut wird sie dann als kleines Binary mit Plugin-System.
Stand Oktober 2026 erkennen wir Monkey HTTP Server auf 17 Websites, und die Erkennungsmethode ist hier wichtiger als die Zahl. Die Identifizierung eines Servers beruht auf dem Banner, das ein Host in seinen Antwort-Headern zurückgibt und das leer, von einem Proxy umgeschrieben oder absichtlich irreführend gesetzt sein kann. Eingebettete Geräte stehen zudem häufig hinter einem Reverse Proxy oder einem CDN, und dann gibt sich nach außen nur der Proxy zu erkennen, während der kleine Server dahinter nie auftaucht. Geräte an einem Heimanschluss, in einem privaten Netzwerk oder solche, die nur über eine Adresse statt über einen von uns gecrawlten Namen erreichbar sind, tauchen in unseren Daten überhaupt nicht auf. Durch jeden dieser Fälle liegt der tatsächliche Bestand über dem, was wir ausweisen, und keiner drückt ihn darunter.
Der praktische Nutzen einer solchen Liste ist begrenzt, aber handfest. Wenn Sie für Embedded Linux entwickeln, ist die Menge der Hostnamen, die mit diesem Server antworten, eine Karte davon, wer ihn in einem Produkt ausliefert und welche Firmware-Familien offen im Internet gelandet sind. Wenn Sie Schwachstellen erforschen, entspricht Software, die aus dem Jahr 2001 stammt und in einer Handvoll festgeschriebener Builds auftaucht, genau dem Profil von Code, der in Hardware ausgeliefert und nach dem Zeitplan des Hardwareherstellers gepatcht wird statt nach dem des Projekts, sofern er überhaupt gepatcht wird. Eine Domain zu prüfen, die man bereits kennt, beantwortet keine der beiden Fragen. Für jede von ihnen braucht man den gesamten Bestand samt Hosting und Geografie jedes Hosts, was der Download liefert, eine Einzelabfrage aber nicht.
Häufig gestellte Fragen
Wie viele Websites nutzen Monkey HTTP Server?
webatla erkennt Monkey HTTP Server auf 17 Websites, täglich aktualisiert, jede mit Domain, DNS, WHOIS, IP, Land und Ranking.
Kann ich die Liste der Websites herunterladen, die Monkey HTTP Server nutzen?
Ja, als strukturiertes JSONL. Holen Sie sich zuerst eine kostenlose Probe.
Was ist je Site enthalten, und wie aktuell ist es?
Domain, DNS, RDAP/WHOIS, der vollständige Tech-Stack, IP & Land, PageRank und Harmonic, täglich neu erkannt und neu exportiert.
Wie finde ich die Websites, die Monkey HTTP Server nutzen?
Kaufen Sie den Technologie-Datensatz und laden Sie die vollständige Liste der Domains herunter, auf denen wir Monkey HTTP Server erkennen, jeden Tag neu exportiert.
Was steckt sonst noch in den Technologiedaten zu Monkey HTTP Server?
Jede Zeile stellt Monkey HTTP Server neben die anderen Technologien derselben Site, dazu DNS, WHOIS, IP, Land und Ranking.
Kann ich nur die Sites mit Monkey HTTP Server herunterladen oder die gesamte Datenbank?
Beides. Jede Site mit Monkey HTTP Server steckt im Datensatz Technologies, einer herunterladbaren Datei. Oder kaufen Sie All data für die gesamte Datenbank: Technologien plus Identität, Ranking, DNS und RDAP/WHOIS für jede Domain, kombiniert in einer Datei. Täglich frischer Export.
Wie lade ich die Liste der Websites herunter, die Monkey HTTP Server nutzen?
Drei Schritte: (1) Holen Sie sich die kostenlose Probe mit 10.000 Zeilen, um das Schema zu prüfen, (2) kaufen Sie den Datensatz Technologies, (3) laden Sie die vollständige Liste aller Domains herunter, auf denen wir Monkey HTTP Server erkennen, als JSON-Lines-Datei. Sie wird täglich neu exportiert, Sie können die frischeste Liste also jederzeit innerhalb Ihres Zugangszeitraums erneut herunterladen. Jede Zeile enthält die Domain sowie DNS, WHOIS, IP, Hosting-Land und Rang.
Holen Sie sich die vollständige Liste der Websites, die Monkey HTTP Server nutzen
Wählen Sie den Datensatz, der Ihren Bedarf abdeckt. Jeder enthält Monkey HTTP Server und wird als JSONL geliefert, täglich neu aufgebaut.
Der vollständige Technologie-Stack jeder Website, von CMS und Zahlungen bis zu Analytics und Frameworks.
Alles, was wir haben, in einem Paket. Das vollständige webatla-Universum.
Möchten Sie alle Datensätze direkt vergleichen? Zur Preisseite