Télécharger les sites web qui utilisent Monkey HTTP Server
17 sites actifs utilisant Monkey HTTP Server en ce moment
Web servers · depuis 2001 · open source
Aperçu des datasets des sites Monkey HTTP Server
La détection de Monkey HTTP Server est une valeur dans la colonne Technologies . Deux datasets la contiennent, basculez entre eux pour comparer ce qui est inclus.
| 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 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
Répartition des versions
Versions de Monkey HTTP Server détectées sur l’ensemble des 17 sites.
| Version | Sites | Part |
|---|---|---|
| 1.6.8 | 1 | 100.0% |
Le dataset Monkey HTTP Server
Chaque site sur lequel nous avons détecté Monkey HTTP Server, avec version, hébergement, pays, TLD et rang de trafic.
Monkey HTTP Server est présent dans 2 datasets
La détection de Monkey HTTP Server fait partie de Technologies (€159/mois) et All data (€599/mois). Achetez l’un des deux pour filtrer la liste complète de 17 sites, ou récupérez d’abord un aperçu gratuit.
À propos de Monkey HTTP Server
Un logiciel serveur montre normalement une longue traîne de versions, parce que chaque exploitant met à jour selon son propre calendrier et que les anciennes compilations s’attardent pendant des années. Une dispersion de versions aussi plate désigne plutôt des installations arrivées une fois, à l’intérieur d’autre chose, et jamais retouchées. La compilation que nous voyons le plus souvent est 1.6.8.
Le produit est écrit en C et publié sous licence Apache 2.0, et il date de 2001, ce qui le rend plus ancien qu’une bonne partie de ce qui l’accompagne dans la catégorie Web servers. Les serveurs compacts écrits en C existent parce qu’il y a des endroits où un serveur généraliste ne tient pas. Les équipements dédiés, les routeurs, les bornes, les automates industriels et tout ce dont la mémoire se compte en mégaoctets et où aucun administrateur ne se connectera jamais ont malgré tout besoin d’une interface HTTP, et un petit binaire doté d’un système d’extensions est la façon dont cette interface se construit.
En octobre 2026 nous détectons Monkey HTTP Server sur 17 sites, et la méthode de détection compte ici davantage que le décompte lui-même. L’identification d’un serveur repose sur la bannière qu’un hôte renvoie dans ses en-têtes de réponse, laquelle peut être vide, réécrite par un proxy, ou réglée à dessein sur quelque chose de trompeur. Les équipements embarqués sont aussi fréquemment placés derrière un proxy inverse ou un CDN, auquel cas la porte d’entrée annonce le proxy et le petit serveur situé derrière n’apparaît jamais. Un appareil sur une connexion résidentielle, sur un réseau privé, ou joignable seulement par adresse et non par un nom que nous explorons, sort entièrement de nos données. Chacun de ces cas pousse le parc réellement installé au-dessus de ce que nous rapportons, et aucun ne le pousse vers le bas.
L’usage pratique d’une telle liste est étroit et bien réel. Si vous développez pour Linux embarqué, l’ensemble des noms d’hôtes qui répondent avec ce serveur est une carte de qui l’embarque dans un produit et de quelles familles de micrologiciels se sont retrouvées exposées à l’internet ouvert. Si vous cherchez des vulnérabilités, un logiciel qui date de 2001 et qui n’apparaît que dans une poignée de compilations figées correspond exactement au profil du code livré à l’intérieur d’un matériel et corrigé au calendrier du fabricant plutôt qu’à celui du projet, si tant est qu’il soit corrigé. Vérifier un domaine que vous connaissez déjà ne répond ni à l’une ni à l’autre question. Répondre à l’une ou à l’autre exige la population entière, avec l’hébergement et la géographie attachés à chaque hôte, ce que le téléchargement fournit et qu’une requête ne peut pas donner.
Questions fréquentes
Combien de sites web utilisent Monkey HTTP Server ?
webatla détecte Monkey HTTP Server sur 17 sites web, actualisés chaque jour, chacun avec son domaine, DNS, WHOIS, IP, pays et ranking.
Puis-je télécharger la liste des sites web utilisant Monkey HTTP Server ?
Oui, sous forme de JSONL structuré. Récupérez d’abord un échantillon gratuit.
Qu’est-ce qui est inclus pour chaque site, et quelle est sa fraîcheur ?
Domaine, DNS, RDAP/WHOIS, la stack technique complète, IP et pays, PageRank et Harmonic, redétectés et réexportés chaque jour.
Comment trouver les sites web qui utilisent Monkey HTTP Server ?
Achetez le dataset Technologies, puis téléchargez la liste complète des domaines sur lesquels nous détectons Monkey HTTP Server, réexportée chaque jour.
Que trouve-t-on d’autre dans les données technologiques de Monkey HTTP Server ?
Chaque ligne place Monkey HTTP Server à côté des autres technologies du même site, plus DNS, WHOIS, IP, pays et classement.
Puis-je télécharger uniquement les sites utilisant Monkey HTTP Server, ou la base de données entière ?
Les deux. Chaque site utilisant Monkey HTTP Server figure dans le dataset Technologies, un fichier téléchargeable. Ou achetez All data pour toute la base de données : technologies, plus identité, ranking, DNS et RDAP/WHOIS pour chaque domaine, réunis dans un seul fichier. Export frais chaque jour.
Comment télécharger la liste des sites web qui utilisent Monkey HTTP Server ?
Trois étapes : (1) récupérez l’échantillon gratuit de 10 000 lignes pour examiner le schéma, (2) achetez le dataset Technologies, (3) téléchargez la liste complète de tous les domaines sur lesquels nous détectons Monkey HTTP Server, sous forme de fichier JSON Lines. Elle est réexportée chaque jour, vous pouvez donc retélécharger la liste la plus fraîche à tout moment pendant votre période d’accès. Chaque ligne contient le domaine ainsi que le DNS, le WHOIS, l’IP, le pays d’hébergement et le rang.
Obtenez la liste complète des sites utilisant Monkey HTTP Server
Choisissez le dataset qui couvre votre besoin. Chacun inclut Monkey HTTP Server et se télécharge en JSONL, reconstruit chaque jour.
La stack technique complète de chaque site : CMS, paiements, analytics, frameworks.
Tout ce que nous avons, en un seul pack. L’univers webatla dans son intégralité.
Vous voulez comparer tous les datasets côte à côte ? Voir la page des tarifs