Descargar sitios web que utilizan Monkey HTTP Server
17 sitios activos que usan Monkey HTTP Server ahora mismo
Web servers · desde 2001 · open source
Vista previa de los datasets de sitios Monkey HTTP Server
La detección de Monkey HTTP Server es un valor de la columna Technologies . Dos datasets la incluyen, cambie entre ambos para comparar qué incluye cada uno.
| 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 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
Distribución de versiones
Versiones de Monkey HTTP Server detectadas en los 17 sitios.
| Versión | Sitios | Cuota |
|---|---|---|
| 1.6.8 | 1 | 100.0% |
El dataset Monkey HTTP Server
Todos los sitios que hemos detectado utilizando Monkey HTTP Server, con versión, hosting, país, TLD y ranking de tráfico.
Monkey HTTP Server está presente en 2 datasets
La detección de Monkey HTTP Server forma parte de Technologies (€159/mes) y All data (€599/mes). Compre cualquiera de los dos para filtrar la lista completa de 17 sitios, o consiga antes una vista previa gratuita.
Acerca de Monkey HTTP Server
El software de servidor muestra normalmente una larga cola de versiones, porque cada operador actualiza según un calendario distinto y las compilaciones antiguas perduran durante años. Un reparto de versiones tan plano apunta en cambio a instalaciones que llegaron una vez, como parte de otra cosa, y que nunca se volvieron a tocar. La compilación que vemos con más frecuencia es 1.6.8.
El producto está escrito en C y se publica con licencia Apache 2.0, y data de 2001, lo que lo hace más antiguo que buena parte de la categoría Web servers junto a la que figura. Los servidores compactos escritos en C existen porque hay lugares donde un servidor de propósito general no encaja. Los equipos dedicados, los routers, los quioscos, los controladores industriales y cualquier otro sitio donde la memoria se cuenta en megabytes y donde ningún administrador va a iniciar sesión jamás necesitan de todos modos una interfaz HTTP, y un binario pequeño con un sistema de plugins es la forma en que esa interfaz se construye.
En octubre de 2026 detectamos Monkey HTTP Server en 17 sitios, y aquí el método de detección importa más que el recuento. La identificación del servidor descansa en el banner que un host devuelve en sus cabeceras de respuesta, que puede estar vacío, reescrito por un proxy o configurado a propósito con un valor engañoso. Los dispositivos embebidos se colocan además con frecuencia detrás de un proxy inverso o de una CDN, en cuyo caso la puerta de entrada anuncia el proxy y el pequeño servidor que hay detrás no aparece nunca. Un dispositivo en una conexión residencial, en una red privada o accesible solo por dirección y no por un nombre que rastreemos queda por completo fuera de nuestros datos. Cada uno de esos casos empuja la base instalada real por encima de lo que publicamos, y ninguno la empuja hacia abajo.
El uso práctico de una lista como esta es acotado y real. Si desarrolla para Linux embebido, el conjunto de nombres de host que responden con este servidor es un mapa de quién lo incluye dentro de un producto y de qué familias de firmware acabaron expuestas a la internet abierta. Si investiga vulnerabilidades, un software que data de 2001 y que aparece en un puñado de compilaciones fijadas es exactamente el perfil del código que se entrega dentro del hardware y que se parchea según el calendario del fabricante del hardware y no según el del proyecto, si es que se parchea siquiera. Comprobar un dominio que ya conoce no responde a ninguna de las dos preguntas. Responder a cualquiera de ellas exige la población entera, junto con el alojamiento y la geografía asociados a cada host, que es lo que la descarga ofrece y una consulta no puede dar.
Preguntas frecuentes
¿Cuántos sitios web usan Monkey HTTP Server?
webatla detecta Monkey HTTP Server en 17 sitios web, actualizados a diario, cada uno con su dominio, DNS, WHOIS, IP, país y clasificación.
¿Puedo descargar la lista de sitios web que usan Monkey HTTP Server?
Sí, en formato JSONL estructurado. Consiga antes una muestra gratuita.
¿Qué incluye cada sitio, y con qué frecuencia se actualiza?
Dominio, DNS, RDAP/WHOIS, la stack tecnológica completa, IP & país, PageRank y Harmonic, redetectados y reexportados a diario.
¿Cómo encuentro los sitios web que utilizan Monkey HTTP Server?
Compre el dataset Technologies y descargue la lista completa de dominios en los que detectamos Monkey HTTP Server, reexportada cada día.
¿Qué más incluyen los datos de tecnología de Monkey HTTP Server?
Cada fila coloca Monkey HTTP Server junto a las demás tecnologías del mismo sitio, además de DNS, WHOIS, IP, país y clasificación.
¿Puedo descargar solo los sitios que utilizan Monkey HTTP Server, o la base de datos completa?
Ambos. Cada sitio que usa Monkey HTTP Server figura en el dataset Technologies, un archivo descargable. O compre All data para toda la base de datos: tecnologías, más identidad, ranking, DNS y RDAP/WHOIS para cada dominio, reunidos en un solo archivo. Exportación actualizada a diario.
¿Cómo descargo la lista de sitios web que utilizan Monkey HTTP Server?
Tres pasos: (1) consiga la muestra gratuita de 10.000 filas para examinar el esquema, (2) compre el dataset Technologies, (3) descargue la lista completa de todos los dominios en los que detectamos Monkey HTTP Server, en forma de archivo JSON Lines. Se reexporta a diario, así que puede volver a descargar la lista más reciente en cualquier momento dentro de su periodo de acceso. Cada fila contiene el dominio junto con el DNS, el WHOIS, la IP, el país de alojamiento y la clasificación.
Consiga la lista completa de sitios web que usan Monkey HTTP Server
Elija el dataset que cubra lo que necesita. Cada uno incluye Monkey HTTP Server y se descarga en JSONL, reconstruido a diario.
El stack tecnológico completo de cada sitio: CMS, pagos, analítica, frameworks.
Todo lo que tenemos, en un solo paquete. El universo webatla completo.
¿Quiere comparar todos los datasets uno junto al otro? Ver la página de precios
Tecnologías relacionadas
