Descargar sitios web que utilizan microCMS
572 sitios activos que usan microCMS ahora mismo
CMS · de microCMS Inc. · desde 2019 · Proprietary
Vista previa de los datasets de sitios microCMS
La detección de microCMS 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wmg2027.jp | jp | jp | ICANN | HTTP 200 | 104.21.74.203 | US | {"facebook":["https://facebook.com/wmg2027kansai"],"instagram":["https://instagram.com/wmg2027_kansai"],"x-twitter":["https://x.com/wmg2027kansai?s=21","https://x.com/XcorpJP"]} | 2026-09-22 | Google Analytics G-ZLCSGKNGVN UA-57131428-1 +1, Google Tag Manager GTM-5LLXLHM, HSTS, Astro 5.13.5, Slick, cdnjs, HTTP/3, jQuery 3.7.1, Favicon, microCMS | 0.000000184832 | 13,189,533 | 2022-12-22 | 2026-12-31 |
| tajima.jp | jp | jp | ICANN | HTTP 200 | 35.76.35.251 | JP | {"youtube":["https://youtube.com/user/TajimaRoofing"]} | 2026-09-20 | Google Analytics G-4430WLSLQT G-WEJC1X2S4W UA-15913471-7 +2, HTTP/2, Favicon, microCMS, Amazon S3, GlobalSign, Open Graph, Amazon CloudFront, Microsoft Clarity, Amazon Web Services | 0.000000167076 | 13,304,667 | 2019-09-11 | 2026-09-30 |
| yokohamafc.com | com | com | ICANN | HTTP 200 | 34.8.137.92 | US | {"tiktok":["https://tiktok.com/@yokohamafc_official"],"youtube":["https://youtube.com/channel/UCUiRzm2iBaQM8k_TccZDq-w","https://youtube.com/channel/UCUiRzm2iBaQM8k_TccZDq-w?sub_confirmation=1"],"facebook":["https://facebook.com/yokohamafc1999"],"instagram":["https://instagram.com/yokohamafc_official"],"x-twitter":["https://twitter.com/yokohama_fc","https://x.com/yokohama_fc","https://twitter.com/fc_fulimaru"]} | 2026-09-23 | React, HTTP/3, Favicon, Next.js, Node.js, Webpack, microCMS, Open Graph, Google Cloud, Priority Hints | 0.000000132366 | 14,255,148 | 1999-02-27 | 2027-02-27 |
| bill-one.com | com | com | ICANN | HTTP 200 | 108.138.26.117 | US | {"youtube":["https://youtube.com/user/SansanInc"],"facebook":["https://facebook.com/SansanJapan"],"x-twitter":["https://x.com/SansanJapan"]} | 2026-09-29 | HubSpot 8386116, Google Ads AW-574412460, Google Analytics G-9XV8F686BP G-B334YYRM8C G-C5D0MCRKPD G-M2HWH718CN G-MYBDMZNDSX G-VZS4WM8S73 +5, HTTP/2, Favicon, microCMS, Amazon S3, Open Graph, Facebook Pixel, Priority Hints | 0.00000010067 | 16,309,953 | 2019-12-10 | 2026-12-10 |
| algomatic.jp | jp | jp | ICANN | HTTP 200 | 76.76.21.21 | US | {"facebook":["https://facebook.com/hiroto.kamoi.1","https://facebook.com/reds.tkaotuutmai"],"linkedin":["https://linkedin.com/in/hirotokamoi"],"x-twitter":["https://x.com/hktech94","https://x.com/dory111111","https://x.com/hiroyuki_takah"]} | 2026-09-26 | HubSpot 244869827, Google Analytics G-62W376RWH4, HSTS, Astro 7.3.2, HTTP/2, OpenAI, Vercel, Favicon, Sendgrid, microCMS | 0.0000000910747 | 13,859,131 | 2023-03-30 | 2027-03-31 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wmg2027.jp | jp | jp | ICANN | HTTP 200 | 104.21.74.203 | US | {"facebook":["https://facebook.com/wmg2027kansai"],"instagram":["https://instagram.com/wmg2027_kansai"],"x-twitter":["https://x.com/wmg2027kansai?s=21","https://x.com/XcorpJP"]} | 2026-09-22 | Google Analytics G-ZLCSGKNGVN UA-57131428-1 +1, Google Tag Manager GTM-5LLXLHM, HSTS, Astro 5.13.5, Slick, cdnjs, HTTP/3, jQuery 3.7.1, Favicon, microCMS | 2026-09-28 | TRUE | {"A":["104.21.74.203","172.67.206.60"],"MX":[{"host":"mail.wmg2027.jp","priority":10}],"NS":["magnolia.ns.cloudflare.com","owen.ns.cloudflare.com"],"SOA":{"mname":"magnolia.ns.cloudflare.com","retry":2400,"rname":"dns.cloudflare.com","expire":604800,"serial":2414818688,"minimum":1800,"refresh":10000},"TXT":["google-site-verification=4gmlYugP1KY-urAVYui1MlfnFeVSijEp9R4jLGpAmL0","v=spf1 a:www3097.sakura.ne.jp mx:wmg2027.jp ip4:49.212.207.107 ip4:161.34.84.13 include:spf.haihaimail.jp ~all"],"AAAA":["2606:4700:3031::6815:4acb","2606:4700:3035::ac43:ce3c"],"HTTPS":[{"params":["alpn=h3,h2","ipv4hint=104.21.74.203,172.67.206.60","ech=AEX+DQBB7QAgACAB/s5wDktZzfurFSNLXVXsBbadZH/7182blkILBW1nRQAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA=","ipv6hint=2606:4700:3031::6815:4acb,2606:4700:3035::ac43:ce3c"],"target":"","priority":1}]} | 0.000000184832 | 13,189,533 | 2026-01-07 | WHOIS | 2022-12-22 | 2026-12-31 | 2026-01-01 | The Organizing Committee of the World Masters Games 2021 Kansai | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] WMG2027.JP\r\n\r\n[Registrant] The Organizing Committee of the World Masters Games 2021 Kansai\r\n\r\n[Name Server] magnolia.ns.cloudflare.com\r\n[Name Server] owen.ns.cloudflare.com\r\n[Signing Key] \r\n\r\n[Created on] 2022/12/22\r\n[Expires on] 2026/12/31\r\n[Status] Active\r\n[Last Updated] 2026/01/01 16:13:56 (JST)\r\n\r\nContact Information:\r\n[Name] SAKURA internet Inc.\r\n[Email] nic-staff@sakura.ad.jp\r\n[Web Page] \r\n[Postal code] 530-0011\r\n[Postal Address] Osaka\r\n Osaka\r\n GRAND GREEN OSAKA North, JAM BASE, 3F 6-38 Ofukacho, Kita-ku\r\n[Phone] 06-6476-8790\r\n[Fax] \r\n\r\n"} | Domain is active |
| tajima.jp | jp | jp | ICANN | HTTP 200 | 35.76.35.251 | JP | {"youtube":["https://youtube.com/user/TajimaRoofing"]} | 2026-09-20 | Google Analytics G-4430WLSLQT G-WEJC1X2S4W UA-15913471-7 +2, HTTP/2, Favicon, microCMS, Amazon S3, GlobalSign, Open Graph, Amazon CloudFront, Microsoft Clarity, Amazon Web Services | 2026-09-30 | TRUE | {"A":["35.76.35.251","54.150.223.22"],"MX":[{"host":"mail1020.conoha.ne.jp","priority":10}],"NS":["ns-1495.awsdns-58.org","ns-1876.awsdns-42.co.uk","ns-466.awsdns-58.com","ns-976.awsdns-58.net"],"SOA":{"mname":"ns-1495.awsdns-58.org","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200},"TXT":["_globalsign-domain-verification=U028THFZNQlNkuwjnUODgKsn1N2iqDEGpLfQ4TZAGn","google-site-verification=Y2qEBcwhtwRSt5ksaAngolhNCuJ4e5hGU_O72tdrsyI","v=spf1 ip4:180.222.182.222 ip4:180.222.182.151 ip4:3.113.64.146 include:_spf.conoha.ne.jp -all"]} | 0.000000167076 | 13,304,667 | 2026-09-29 | WHOIS | 2019-09-11 | 2026-09-30 | 2025-10-01 | TAJIMA ROOFING INC. | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] TAJIMA.JP\r\n\r\n[Registrant] TAJIMA ROOFING INC.\r\n\r\n[Name Server] ns-466.awsdns-58.com\r\n[Name Server] ns-1495.awsdns-58.org\r\n[Name Server] ns-1876.awsdns-42.co.uk\r\n[Name Server] ns-976.awsdns-58.net\r\n[Signing Key] \r\n\r\n[Created on] 2019/09/11\r\n[Expires on] 2026/09/30\r\n[Status] Active\r\n[Lock Status] DomainTransferLocked\r\n[Lock Status] AgentChangeLocked\r\n[Last Updated] 2025/10/01 01:05:04 (JST)\r\n\r\nContact Information:\r\n[Name] GOTO KEITA\r\n[Email] goto-k@tajima.co.jp\r\n[Web Page] \r\n[Postal code] 101-8575\r\n[Postal Address] 3-11-13 Iwamoto-cho Chiyoda-ku\r\n[Phone] 03-5821-7711\r\n[Fax]"} | Domain is active |
| yokohamafc.com | com | com | ICANN | HTTP 200 | 34.8.137.92 | US | {"tiktok":["https://tiktok.com/@yokohamafc_official"],"youtube":["https://youtube.com/channel/UCUiRzm2iBaQM8k_TccZDq-w","https://youtube.com/channel/UCUiRzm2iBaQM8k_TccZDq-w?sub_confirmation=1"],"facebook":["https://facebook.com/yokohamafc1999"],"instagram":["https://instagram.com/yokohamafc_official"],"x-twitter":["https://twitter.com/yokohama_fc","https://x.com/yokohama_fc","https://twitter.com/fc_fulimaru"]} | 2026-09-23 | React, HTTP/3, Favicon, Next.js, Node.js, Webpack, microCMS, Open Graph, Google Cloud, Priority Hints | 2026-09-18 | TRUE | {"A":["34.8.137.92"],"MX":[{"host":"alt1.aspmx.l.google.com","priority":5},{"host":"alt2.aspmx.l.google.com","priority":5},{"host":"alt3.aspmx.l.google.com","priority":10},{"host":"alt4.aspmx.l.google.com","priority":10},{"host":"aspmx.l.google.com","priority":1}],"NS":["ns-1314.awsdns-36.org","ns-1625.awsdns-11.co.uk","ns-214.awsdns-26.com","ns-652.awsdns-17.net"],"SOA":{"mname":"ns-652.awsdns-17.net","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200},"TXT":["google-site-verification=LvpJTD5mYV4ISIrAkKsafxi3PkXtWy9aD-6VAZQoWec","v=spf1 mx include:_spf.google.com include:crmstyle.com include:spf-bma.mpme.jp include:spf2.nlk2.smtps.jp include:spf.nucleus.jp include:mktomail.com ip4:59.106.171.23 ip4:202.229.236.164 ip4:210.254.139.121 ip4:211.128.73.121 ip4:210.254.139.122 ip4:211.128.73.122 ip4:210.254.139.123 ip4:211.128.73.123 ip4:210.254.139.124 ip4:211.128.73.124 ip4:210.254.139.13 ip4:211.128.73.13 ip4:210.175.91.224 ip4:202.248.11.9 ip4:202.248.11.10 ip4:218.216.82.132 ~all"]} | 0.000000132366 | 14,255,148 | 2026-03-28 | RDAP | 1999-02-27 | 2027-02-27 | 2026-03-28 | GMO Internet Group, Inc. d/b/a Onamae.com | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/com/v1/domain/YOKOHAMAFC.COM","type":"application/rdap+json","value":"https://rdap.verisign.com/com/v1/domain/YOKOHAMAFC.COM"},{"rel":"related","href":"https://rdap.gmo-onamae.com/rdap/v1/domain/YOKOHAMAFC.COM","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/domain/YOKOHAMAFC.COM"}],"events":[{"eventDate":"1999-02-27T05:00:00Z","eventAction":"registration"},{"eventDate":"2027-02-27T05:00:00Z","eventAction":"expiration"},{"eventDate":"2026-02-11T15:57:19Z","eventAction":"last changed"},{"eventDate":"2026-03-28T14:01:22Z","eventAction":"last update of RDAP database"}],"handle":"3952461_DOMAIN_COM-VRSN","status":["active"],"ldhName":"YOKOHAMAFC.COM","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml","type":"text/html","value":"https://rdap.verisign.com/com/v1/domain/yokohamafc.com"}],"title":"Terms of Service","description":["Service subject to Terms of Use."]},{"links":[{"href":"https://icann.org/epp","type":"text/html"}],"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":"text/html","value":"https://rdap.verisign.com/com/v1/domain/yokohamafc.com"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"about","href":"http://gmo.jp","type":"text/html","value":"https://rdap.gmo-onamae.com/rdap/v1/"}],"roles":["registrar"],"handle":"49","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+81.337709199"],["email",{},"text","abuse@internet.gmo"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"49"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GMO Internet Group, Inc. d/b/a Onamae.com"]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS-1314.AWSDNS-36.ORG","objectClassName":"nameserver"},{"ldhName":"NS-1625.AWSDNS-11.CO.UK","objectClassName":"nameserver"},{"ldhName":"NS-214.AWSDNS-26.COM","objectClassName":"nameserver"},{"ldhName":"NS-652.AWSDNS-17.NET","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| bill-one.com | com | com | ICANN | HTTP 200 | 108.138.26.117 | US | {"youtube":["https://youtube.com/user/SansanInc"],"facebook":["https://facebook.com/SansanJapan"],"x-twitter":["https://x.com/SansanJapan"]} | 2026-09-29 | HubSpot 8386116, Google Ads AW-574412460, Google Analytics G-9XV8F686BP G-B334YYRM8C G-C5D0MCRKPD G-M2HWH718CN G-MYBDMZNDSX G-VZS4WM8S73 +5, HTTP/2, Favicon, microCMS, Amazon S3, Open Graph, Facebook Pixel, Priority Hints | 2026-10-02 | TRUE | {"A":["108.138.26.117","108.138.26.124","108.138.26.44","108.138.26.53"],"MX":[{"host":"mx.sendgrid.net","priority":10}],"NS":["ns-1437.awsdns-51.org","ns-1848.awsdns-39.co.uk","ns-428.awsdns-53.com","ns-536.awsdns-03.net"],"SOA":{"mname":"ns-428.awsdns-53.com","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200},"TXT":["google-site-verification=NuGwIqCbsjlSZhjrY-QeJbQ_xIGrb4I2qQM1BJlv_Es","google-site-verification=aU_ii8hbTLf2vC8j79HgmbEhDvWwincxVIGzfnGTSR0","google-site-verification=alOjN1Y0TwVP1uOEN7yHS48PXvaM2jyK-cCkPUA-fiY","google-site-verification=rxJt9xuVaawosWZjJeHhXCxnX8kQ_VJv9nfIQ2jp_ic","google-site-verification=tUQ7uZ2cixgXrSrOHJfsYPOQMLkHH2SsDCMTz0e3pxM","google-site-verification=tqhkWwAevQ7e9-EBkMOGZ9HhJbQKQDP1uhqbtat3vkIgoogle-site-verification=tqhkWwAevQ7e9-EBkMOGZ9HhJbQKQDP1uhqbtat3vkI","v=spf1 -all"]} | 0.00000010067 | 16,309,953 | 2025-11-25 | RDAP | 2019-12-10 | 2026-12-10 | 2025-11-25 | GMO Internet Group, Inc. d/b/a Onamae.com | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/com/v1/domain/BILL-ONE.COM","type":"application/rdap+json","value":"https://rdap.verisign.com/com/v1/domain/BILL-ONE.COM"},{"rel":"related","href":"https://rdap.gmo-onamae.com/rdap/v1/domain/BILL-ONE.COM","type":"application/rdap+json","value":"https://rdap.gmo-onamae.com/rdap/v1/domain/BILL-ONE.COM"}],"events":[{"eventDate":"2019-12-10T06:57:32Z","eventAction":"registration"},{"eventDate":"2026-12-10T06:57:32Z","eventAction":"expiration"},{"eventDate":"2025-11-24T15:41:42Z","eventAction":"last changed"},{"eventDate":"2025-11-25T06:29:54Z","eventAction":"last update of RDAP database"}],"handle":"2465412632_DOMAIN_COM-VRSN","status":["active"],"ldhName":"BILL-ONE.COM","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml","type":"text/html","value":"https://rdap.verisign.com/com/v1/domain/bill-one.com"}],"title":"Terms of Service","description":["Service subject to Terms of Use."]},{"links":[{"href":"https://icann.org/epp","type":"text/html"}],"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":"text/html","value":"https://rdap.verisign.com/com/v1/domain/bill-one.com"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"about","href":"http://gmo.jp","type":"text/html","value":"https://rdap.gmo-onamae.com/rdap/v1/"}],"roles":["registrar"],"handle":"49","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+81.337709199"],["email",{},"text","abuse@internet.gmo"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"49"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GMO Internet Group, Inc. d/b/a Onamae.com"]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS-1437.AWSDNS-51.ORG","objectClassName":"nameserver"},{"ldhName":"NS-1848.AWSDNS-39.CO.UK","objectClassName":"nameserver"},{"ldhName":"NS-428.AWSDNS-53.COM","objectClassName":"nameserver"},{"ldhName":"NS-536.AWSDNS-03.NET","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| algomatic.jp | jp | jp | ICANN | HTTP 200 | 76.76.21.21 | US | {"facebook":["https://facebook.com/hiroto.kamoi.1","https://facebook.com/reds.tkaotuutmai"],"linkedin":["https://linkedin.com/in/hirotokamoi"],"x-twitter":["https://x.com/hktech94","https://x.com/dory111111","https://x.com/hiroyuki_takah"]} | 2026-09-26 | HubSpot 244869827, Google Analytics G-62W376RWH4, HSTS, Astro 7.3.2, HTTP/2, OpenAI, Vercel, Favicon, Sendgrid, microCMS | 2026-10-01 | TRUE | {"A":["76.76.21.21"],"MX":[{"host":"smtp.google.com","priority":1}],"NS":["hayes.ns.cloudflare.com","sloan.ns.cloudflare.com"],"SOA":{"mname":"hayes.ns.cloudflare.com","retry":2400,"rname":"dns.cloudflare.com","expire":604800,"serial":2414917800,"minimum":1800,"refresh":10000},"TXT":["google-site-verification=yOhgj1-tXRFas-AwUEnOisEPo53luGLiyHMaFIKRn2M","openai-domain-verification=dv-0ONz2JsqxP5rZ1uOYbQHrFuA","v=spf1 include:_spf.google.com include:sendgrid.net include:47335347.spf01.hubspotemail.net include:spf.mta.hdems.com ~all"]} | 0.0000000910747 | 13,859,131 | 2026-04-17 | WHOIS | 2023-03-30 | 2027-03-31 | 2026-04-16 | — | {"raw_response":"[ JPRS database provides information on network administration. Its use is ]\r\n[ restricted to network administration purposes. For further information, ]\r\n[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]\r\n[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]\r\nDomain Information:\r\n[Domain Name] ALGOMATIC.JP\r\n\r\n[Registrant] Algomatic\r\n\r\n[Name Server] sloan.ns.cloudflare.com\r\n[Name Server] hayes.ns.cloudflare.com\r\n[Signing Key] \r\n\r\n[Created on] 2023/03/30\r\n[Expires on] 2027/03/31\r\n[Status] Active\r\n[Last Updated] 2026/04/16 15:40:26 (JST)\r\n\r\nContact Information:\r\n[Name] Algomatic\r\n[Email] hagihara-ryosuke@kcgrp.jp\r\n[Web Page] \r\n[Postal code] 106-0032\r\n[Postal Address] Tokyo Minato 3-2-1\r\n Roppongi\r\n[Phone] +81.365553630\r\n[Fax]"} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
El dataset microCMS
Todos los sitios que hemos detectado utilizando microCMS, con versión, hosting, país, TLD y ranking de tráfico.
microCMS está presente en 2 datasets
La detección de microCMS forma parte de Technologies (€159/mes) y All data (€599/mes). Compre cualquiera de los dos para filtrar la lista completa de 572 sitios, o consiga antes una vista previa gratuita.
Acerca de microCMS
Un gestor de contenidos headless, que nuestro índice archiva bajo la etiqueta CMS, está construido para ser invisible. El contenido reside detrás de una API, el front end es una aplicación aparte y nada en la página entregada está obligado a decir qué servicio suministró las palabras. microCMS funciona exactamente así, lo que lo convierte en algo insólito de detectar siquiera y en algo sobre lo que conviene ser honesto antes de citar ninguna cifra.
Lanzada en 2019 por microCMS Inc., la plataforma sirve contenido estructurado a través de endpoints REST a lo que sea que renderice el sitio, habitualmente un framework de JavaScript que genera páginas estáticas en el momento del despliegue. Los equipos de producto japoneses adoptaron el modelo pronto, y su implantación creció junto al movimiento más amplio hacia front ends prerrenderizados en ese mercado. La plataforma tiene licencia Proprietary y está alojada por el proveedor, se ofrece con un plan de entrada gratuito y con suscripciones de pago por encima, así que una detección implica una cuenta con el proveedor y no un paquete descargado.
La detección depende por completo de lo que deje atrás el front end. Los nombres de host de la API incrustados en el código del lado del cliente, los medios servidos desde los dominios de la propia plataforma, los parámetros de vista previa y las referencias a las herramientas de compilación son las huellas prácticas. Un sitio que sirve las imágenes a través de su propia CDN y que solo recupera el contenido en tiempo de compilación puede funcionar íntegramente con microCMS y parecer HTML estático corriente desde fuera. En octubre de 2026 lo detectamos en 572 sitios, y esa es una cota inferior con un margen amplio y no una estimación de la base de clientes.
La presencia sigue aportando información, y la información habla sobre todo del equipo y no de la página. Una construcción sobre microCMS implica una arquitectura desacoplada, un flujo de despliegue, desarrolladores cómodos con un método que empieza por la API y un grupo editorial que ha aceptado un panel estructurado en lugar de un maquetador visual de páginas. Las empresas que venden bibliotecas de componentes, alojamiento estático, buscadores, optimización de imágenes, localización o analítica venden justo a ese perfil. Los reclutadores y los analistas de mercado leen la misma detección como prueba de capacidad de ingeniería por cuenta propia, y esa es una pregunta distinta de si el sitio es grande.
Una consulta sobre un dominio zanja una sospecha sobre un sitio. La lista de todos los dominios donde se ha observado microCMS responde a otra pregunta, a saber, hasta dónde se ha extendido la plataforma, cuánto se concentra en un solo mercado y si el recuento se mueve entre exportaciones. Nuestra descarga proporciona esa lista con el resto de la pila detectada de cada sitio adjunta, de modo que la elección de CMS puede cruzarse con framework, alojamiento y país antes de que nadie decida si la población merece la pena.
Preguntas frecuentes
¿Cuántos sitios web usan microCMS?
webatla detecta microCMS en 572 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 microCMS?
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 microCMS?
Compre el dataset Technologies y descargue la lista completa de dominios en los que detectamos microCMS, reexportada cada día.
¿Qué más incluyen los datos de tecnología de microCMS?
Cada fila coloca microCMS 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 microCMS, o la base de datos completa?
Ambos. Cada sitio que usa microCMS 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 microCMS?
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 microCMS, 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 microCMS
Elija el dataset que cubra lo que necesita. Cada uno incluye microCMS 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
