Scaricare i siti web che utilizzano Twitter Emoji (Twemoji)
2.273.688 siti attivi che utilizzano Twitter Emoji (Twemoji) in questo momento
Font scripts · di X Corp · dal 2014 · open source
Anteprima dei dataset dei siti Twitter Emoji (Twemoji)
Il rilevamento di Twitter Emoji (Twemoji) è un valore della colonna Technologies . Due dataset la contengono, passi dall’uno all’altro per confrontare cosa è incluso.
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| microformats.org | org | org | ICANN | HTTP 200 | 45.33.42.194 | US | {"github":["https://github.com/microformats/microformats-parser","https://github.com/indieweb/php-mf2","https://github.com/microformats/mf2py"],"x-twitter":["https://t.co/ZCE7rTKmPa"]} | 2026-10-08 | Google Analytics UA-1889385-1, PHP, RSS, MySQL, Nginx 1.17.10, Ubuntu, Favicon, Gravatar, WordPress 5.4.24, Twitter Emoji (Twemoji) | 0.000133867 | 17,823,662 | 2005-01-26 | 2027-01-26 |
| rutube.ru | ru | ru | ICANN | HTTP 200 | 109.238.90.239 | RU | {"ok":["https://ok.ru/rutube"],"vk":["https://vk.com/rutube"],"telegram":["https://t.me/rutube"]} | 2026-09-18 | PWA, RSS, Nginx, Favicon, GlobalSign, Open Graph, Twitter Emoji (Twemoji) | 0.0000460209 | 18,341,312 | 2006-10-10 | 2026-10-10 |
| zapisky.info | info | info | ICANN | HTTP 200 | 40.91.223.51 | NL | {"github":["https://github.com/somemove/auth0-nette-extension","https://github.com/auth0/auth0-php"],"x-twitter":["https://twitter.com/jspetrak","http://twitter.com/jurajkovac","http://twitter.com/janzemanek"]} | 2026-09-24 | IIS 10.0, PHP 7.2.7, RSS, MySQL, Vimeo, HTTP/2, jQuery, core-js, EmbedPlus 14.0.1.4, WordPress 5.9.18 | 0.000122476 | 14,876,771 | 2003-10-17 | 2026-10-17 |
| automattic.com | com | com | ICANN | HTTP 200 | 192.0.78.24 | US | {"youtube":["https://youtube.com/c/automattic"],"facebook":["https://facebook.com/WordPresscom","https://facebook.com/AutomatticInc"],"linkedin":["https://linkedin.com/company/automattic"],"x-twitter":["https://x.com/automattic"]} | 2026-09-28 | Google Analytics GA4 G-737CYY5004, PHP, RSS, HSTS, Figma, MySQL, Nginx, HTTP/2, Favicon, HubSpot | 0.0000488536 | 18,038,514 | 2004-06-19 | 2033-06-19 |
| akismet.com | com | com | ICANN | HTTP 200 | 192.0.78.24 | US | {"facebook":["https://facebook.com/WordPresscom"]} | 2026-09-26 | HubSpot 39653948, Google Ads AW-10778599042, Google Analytics GA4 G-V8X5PZE9F8 UA-19309600-2 +1, PHP, RSS, HSTS, MySQL, Nginx, HTTP/2, Favicon | 0.0000341415 | 17,478,466 | 2005-10-11 | 2027-10-11 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| microformats.org | org | org | ICANN | HTTP 200 | 45.33.42.194 | US | {"github":["https://github.com/microformats/microformats-parser","https://github.com/indieweb/php-mf2","https://github.com/microformats/mf2py"],"x-twitter":["https://t.co/ZCE7rTKmPa"]} | 2026-10-08 | Google Analytics UA-1889385-1, PHP, RSS, MySQL, Nginx 1.17.10, Ubuntu, Favicon, Gravatar, WordPress 5.4.24, Twitter Emoji (Twemoji) | 2026-10-02 | TRUE | {"A":["45.33.42.194"],"MX":[{"host":"microformats.org","priority":10}],"NS":["ns1.linode.com","ns2.linode.com","ns3.linode.com","ns4.linode.com","ns5.linode.com"],"SOA":{"mname":"ns1.linode.com","retry":14400,"rname":"hostmaster.microformats.org","expire":1209600,"serial":2021000011,"minimum":86400,"refresh":14400},"TXT":["'v=spf1 a mx ~all'"]} | 0.000133867 | 17,823,662 | 2026-03-29 | RDAP | 2005-01-26 | 2027-01-26 | 2026-01-10 | Domain.com - Network Solutions, LLC | {"raw_response":{"links":[{"rel":"related","href":"https://rdap.snapnames.com/rdap/domain/microformats.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/microformats.org"},{"rel":"self","href":"https://rdap.publicinterestregistry.org/rdap/domain/microformats.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/microformats.org"}],"events":[{"eventDate":"2027-01-26T04:13:04.414Z","eventAction":"expiration"},{"eventDate":"2005-01-26T04:13:04.414Z","eventAction":"registration"},{"eventDate":"2026-01-10T09:05:53.233Z","eventAction":"last changed"},{"eventDate":"2026-03-29T21:52:04.309Z","eventAction":"last update of RDAP database"}],"status":["active"],"ldhName":"microformats.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/microformats.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/microformats.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/microformats.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/886","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/entity/886"},{"rel":"about","href":"https://rdap.snapnames.com/rdap/","type":"application/rdap+json","value":"https://rdap.snapnames.com/rdap/"}],"roles":["registrar"],"handle":"886","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.8777228662"],["email",{},"text","domain.operations@web.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"886"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Domain.com - Network Solutions, LLC"]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"686224d35bb24cf997acf84f2b526cbc-LROR","status":["associated"],"ldhName":"ns1.linode.com","unicodeName":"ns1.linode.com","objectClassName":"nameserver"},{"handle":"60e3c63d632c4abfa3113c500c95e4d5-LROR","status":["associated"],"ldhName":"ns2.linode.com","unicodeName":"ns2.linode.com","objectClassName":"nameserver"},{"handle":"978df9b5b89c464e8681ff2e9b6db15e-LROR","status":["associated"],"ldhName":"ns3.linode.com","unicodeName":"ns3.linode.com","objectClassName":"nameserver"},{"handle":"eaa4ac3d82914f3894ecbc3f5b8ca973-LROR","status":["associated"],"ldhName":"ns4.linode.com","unicodeName":"ns4.linode.com","objectClassName":"nameserver"},{"handle":"4f28aefa3cef4f7382a0de9a3cd07feb-LROR","status":["associated"],"ldhName":"ns5.linode.com","unicodeName":"ns5.linode.com","objectClassName":"nameserver"}],"unicodeName":"microformats.org","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}} | Domain is active |
| rutube.ru | ru | ru | ICANN | HTTP 200 | 109.238.90.239 | RU | {"ok":["https://ok.ru/rutube"],"vk":["https://vk.com/rutube"],"telegram":["https://t.me/rutube"]} | 2026-09-18 | PWA, RSS, Nginx, Favicon, GlobalSign, Open Graph, Twitter Emoji (Twemoji) | 2026-10-06 | TRUE | {"A":["109.238.90.239","178.248.233.148"],"MX":[{"host":"mg01.uma.tech","priority":40},{"host":"mg02.uma.tech","priority":40},{"host":"mg03.uma.tech","priority":40}],"NS":["ns3-l2.nic.ru","ns4-cloud.nic.ru","ns4-l2.nic.ru","ns8-cloud.nic.ru","ns8-l2.nic.ru"],"SOA":{"mname":"ns3-l2.nic.ru","retry":3600,"rname":"dns.nic.ru","expire":2592000,"serial":2021034037,"minimum":600,"refresh":1440},"TXT":["HARICA-mjtv9sdHea9vpunVcTX","_globalsign-domain-verification=JEBPSqoC_mkG0YQBqJuApSbMc6yu_6MynAsFZbOyP8","ngenix-verification=73d5b0c1334e57d9aef4e5aa19513812","tci-dcv=2dc0af62aad0787f158c51965c06b390f2a08fd337271e0dd9d6663d290dbc18","tci-dcv=d91bfac14360e07006be5b3c38611befc60d0320ca7ee20618174fd0429356af","v=spf1 mx ip4:195.246.247.13 ip4:195.246.247.15 ip4:80.249.129.244 ip4:176.118.20.17 ip4:193.232.150.81 ip4:185.171.101.98 ip4:77.244.211.60 -all","yandex-verification: d57a0470dc4efcd5"]} | 0.0000460209 | 18,341,312 | 2026-10-09 | WHOIS | 2006-10-10 | 2026-10-10 | 2025-10-02 | RU-CENTER-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: RUTUBE.RU\nnserver: ns3-l2.nic.ru.\nnserver: ns4-cloud.nic.ru.\nnserver: ns4-l2.nic.ru.\nnserver: ns8-cloud.nic.ru.\nnserver: ns8-l2.nic.ru.\nstate: REGISTERED, DELEGATED, VERIFIED\norg: \ntaxpayer-id: \nregistrar: RU-CENTER-RU\nadmin-contact: https://www.nic.ru/whois\ncreated: 2006-10-10T20:00:00Z\npaid-till: 2026-10-10T21:00:00Z\nfree-date: 2026-11-11\nsource: TCI\n\nLast updated on 2026-10-08T23:03:01Z"} | Domain is active |
| zapisky.info | info | info | ICANN | HTTP 200 | 40.91.223.51 | NL | {"github":["https://github.com/somemove/auth0-nette-extension","https://github.com/auth0/auth0-php"],"x-twitter":["https://twitter.com/jspetrak","http://twitter.com/jurajkovac","http://twitter.com/janzemanek"]} | 2026-09-24 | IIS 10.0, PHP 7.2.7, RSS, MySQL, Vimeo, HTTP/2, jQuery, core-js, EmbedPlus 14.0.1.4, WordPress 5.9.18 | 2026-10-06 | TRUE | {"A":["40.91.223.51"],"NS":["ns.wedos.com","ns.wedos.cz","ns.wedos.eu","ns.wedos.net"],"SOA":{"mname":"ns.wedos.net","retry":1800,"rname":"wedos.wedos.com","expire":1814400,"serial":2022091201,"minimum":3600,"refresh":3600}} | 0.000122476 | 14,876,771 | 2026-03-11 | RDAP | 2003-10-17 | 2026-10-17 | 2026-03-11 | WEDOS Internet, a.s. | {"raw_response":{"links":[{"rel":"related","href":"https://rdap.wedos.com/domain/zapisky.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/zapisky.info"},{"rel":"self","href":"https://rdap.identitydigital.services/rdap/domain/zapisky.info","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/domain/zapisky.info"}],"events":[{"eventDate":"2022-09-12T12:06:05.914Z","eventAction":"transfer"},{"eventDate":"2026-10-17T06:41:29.218Z","eventAction":"expiration"},{"eventDate":"2003-10-17T06:41:29.218Z","eventAction":"registration"},{"eventDate":"2025-12-01T06:42:04.176Z","eventAction":"last changed"},{"eventDate":"2026-03-11T20:36:52.188Z","eventAction":"last update of RDAP database"}],"status":["active"],"ldhName":"zapisky.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/zapisky.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/zapisky.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/zapisky.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/3860","type":"application/rdap+json","value":"https://rdap.identitydigital.services/rdap/entity/3860"},{"rel":"about","href":"https://rdap.wedos.com/","type":"application/rdap+json","value":"https://rdap.wedos.com/"}],"roles":["registrar"],"handle":"3860","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+4.20380999333"],["email",{},"text","abuse@wedos.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"3860"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","WEDOS Internet, a.s."]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"52754d6d33c94456bca77d11ff7c34ef-DONUTS","status":["associated"],"ldhName":"ns.wedos.net","unicodeName":"ns.wedos.net","objectClassName":"nameserver"},{"handle":"5503ae0e20eb4ef2883ca3e174fa9fd9-DONUTS","status":["associated"],"ldhName":"ns.wedos.eu","unicodeName":"ns.wedos.eu","objectClassName":"nameserver"},{"handle":"62586235b16f40cbab26b3be6779c741-DONUTS","status":["associated"],"ldhName":"ns.wedos.cz","unicodeName":"ns.wedos.cz","objectClassName":"nameserver"},{"handle":"cde829d7bc234732a6025c0fc562943c-DONUTS","status":["associated"],"ldhName":"ns.wedos.com","unicodeName":"ns.wedos.com","objectClassName":"nameserver"}],"unicodeName":"zapisky.info","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}} | Domain is active |
| automattic.com | com | com | ICANN | HTTP 200 | 192.0.78.24 | US | {"youtube":["https://youtube.com/c/automattic"],"facebook":["https://facebook.com/WordPresscom","https://facebook.com/AutomatticInc"],"linkedin":["https://linkedin.com/company/automattic"],"x-twitter":["https://x.com/automattic"]} | 2026-09-28 | Google Analytics GA4 G-737CYY5004, PHP, RSS, HSTS, Figma, MySQL, Nginx, HTTP/2, Favicon, HubSpot | 2026-10-02 | TRUE | {"A":["192.0.78.24","192.0.78.25"],"MX":[{"host":"mx-ams.automattic.com","priority":10},{"host":"mx-dfw.automattic.com","priority":10}],"NS":["ns1.automattic.com","ns2.automattic.com","ns3.automattic.com","ns4.automattic.com"],"CAA":[{"tag":"issue","flags":0,"value":"letsencrypt.org"}],"SOA":{"mname":"ns1.automattic.com","retry":7200,"rname":"hostmaster.automattic.com","expire":604800,"serial":2023091839,"minimum":60,"refresh":14400},"TXT":["anthropic-domain-verification-q5pmy9=Tj43pQ6DCN1JcMx95QuvpbFG3","atlassian-domain-verification=HLvi8VknRfLwuOZ7TmiaKM8GgOgai45SxxeWZddVaOBMgWielcwit/LmLXXPJm6G","figma-domain-verification=a2e41510ac6b0c5745595c76770385bfd602709c6d04e80ef830c9c482fc9e20-1768211767","google-site-verification=F4jw0P5BvBnjqDSVJEhYv3LEU2WLuqChlBLJEYA2SO0","google-site-verification=l3pF3D6Nfuk18StNUFWXaEEIVTjBWWHvvZYP9sXEAcc","gradle-verification=1AG8E2HVI4P8EOH4BK5URAEO6JVML","spf2.0/mfrom a mx ?all","v=spf1 include:_spf.automattic.com include:mail.zendesk.com include:mg-spf.greenhouse.io include:sendgrid.net include:39653948.spf04.hubspotemail.net ~all","yahoo-verification-key=8dNdxvmgAf9M2eCeh79q5CpzcsN5GkkT9db3Z5Rr3Sk="]} | 0.0000488536 | 18,038,514 | 2025-07-02 | RDAP | 2004-06-19 | 2033-06-19 | 2025-07-01 | MarkMonitor Inc. | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/com/v1/domain/AUTOMATTIC.COM","type":"application/rdap+json","value":"https://rdap.verisign.com/com/v1/domain/AUTOMATTIC.COM"},{"rel":"related","href":"https://rdap.markmonitor.com/rdap/domain/AUTOMATTIC.COM","type":"application/rdap+json","value":"https://rdap.markmonitor.com/rdap/domain/AUTOMATTIC.COM"}],"events":[{"eventDate":"2004-06-19T04:36:05Z","eventAction":"registration"},{"eventDate":"2033-06-19T04:36:05Z","eventAction":"expiration"},{"eventDate":"2023-08-28T07:34:11Z","eventAction":"last changed"},{"eventDate":"2025-07-01T23:19:24Z","eventAction":"last update of RDAP database"}],"handle":"122884515_DOMAIN_COM-VRSN","status":["client delete prohibited","client transfer prohibited","client update prohibited","server delete prohibited","server transfer prohibited","server update prohibited"],"ldhName":"AUTOMATTIC.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/automattic.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/automattic.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://www.markmonitor.com","type":"text/html","value":"https://rdap.markmonitor.com/rdap/"}],"roles":["registrar"],"handle":"292","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.2086851750"],["email",{},"text","abusecomplaints@markmonitor.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"292"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","MarkMonitor Inc."]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS1.AUTOMATTIC.COM","objectClassName":"nameserver"},{"ldhName":"NS2.AUTOMATTIC.COM","objectClassName":"nameserver"},{"ldhName":"NS3.AUTOMATTIC.COM","objectClassName":"nameserver"},{"ldhName":"NS4.AUTOMATTIC.COM","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| akismet.com | com | com | ICANN | HTTP 200 | 192.0.78.24 | US | {"facebook":["https://facebook.com/WordPresscom"]} | 2026-09-26 | HubSpot 39653948, Google Ads AW-10778599042, Google Analytics GA4 G-V8X5PZE9F8 UA-19309600-2 +1, PHP, RSS, HSTS, MySQL, Nginx, HTTP/2, Favicon | 2026-10-02 | TRUE | {"A":["192.0.78.24","192.0.78.25"],"MX":[{"host":"mx1.dfw.automattic.com","priority":10},{"host":"mx2.ams.automattic.com","priority":10}],"NS":["ns1.akismet.com","ns2.akismet.com","ns3.akismet.com","ns4.akismet.com"],"CAA":[{"tag":"issue","flags":0,"value":"letsencrypt.org"}],"SOA":{"mname":"ns1.automattic.com","retry":7200,"rname":"hostmaster.automattic.com","expire":604800,"serial":2023052209,"minimum":300,"refresh":14400},"TXT":["google-site-verification=DZLoR97vlDkw1YUqbLCRXu7tQnJ-8cVnktCsnBwHpCA","google-site-verification=EtOJu7eEjs0n1iFlkpg-e6Zo7gupmWqxRBVwWaeruDU","v=spf1 include:_spf.automattic.com include:sendgrid.net include:ariasystems.net include:mail.zendesk.com -all"]} | 0.0000341415 | 17,478,466 | 2025-09-12 | RDAP | 2005-10-11 | 2027-10-11 | 2025-09-12 | MarkMonitor Inc. | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/com/v1/domain/AKISMET.COM","type":"application/rdap+json","value":"https://rdap.verisign.com/com/v1/domain/AKISMET.COM"},{"rel":"related","href":"https://rdap.markmonitor.com/rdap/domain/AKISMET.COM","type":"application/rdap+json","value":"https://rdap.markmonitor.com/rdap/domain/AKISMET.COM"}],"events":[{"eventDate":"2005-10-11T17:37:40Z","eventAction":"registration"},{"eventDate":"2027-10-11T17:37:40Z","eventAction":"expiration"},{"eventDate":"2025-09-09T09:49:25Z","eventAction":"last changed"},{"eventDate":"2025-09-12T13:33:43Z","eventAction":"last update of RDAP database"}],"handle":"227493890_DOMAIN_COM-VRSN","status":["client delete prohibited","client transfer prohibited","client update prohibited","server delete prohibited","server transfer prohibited","server update prohibited"],"ldhName":"AKISMET.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/akismet.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/akismet.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://www.markmonitor.com","type":"text/html","value":"https://rdap.markmonitor.com/rdap/"}],"roles":["registrar"],"handle":"292","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.2086851750"],["email",{},"text","abusecomplaints@markmonitor.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"292"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","MarkMonitor Inc."]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS1.AKISMET.COM","objectClassName":"nameserver"},{"ldhName":"NS2.AKISMET.COM","objectClassName":"nameserver"},{"ldhName":"NS3.AKISMET.COM","objectClassName":"nameserver"},{"ldhName":"NS4.AKISMET.COM","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
Siti con Twitter Emoji (Twemoji) per paese
| Paese | Siti | Quota |
|---|---|---|
| 🇺🇸 gli Stati Uniti | 1.021.779 | 45,4% |
| 🇩🇪 la Germania | 262.229 | 11,7% |
| 🇯🇵 il Giappone | 131.247 | 5,8% |
| 🇫🇷 la Francia | 115.798 | 5,1% |
| 🇮🇹 l’Italia | 82.156 | 3,7% |
Il dataset Twitter Emoji (Twemoji)
Tutti i siti in cui abbiamo rilevato l’uso di Twitter Emoji (Twemoji), con versione, hosting, paese, TLD e ranking di traffico.
Twitter Emoji (Twemoji) è presente in 2 dataset
Il rilevamento di Twitter Emoji (Twemoji) fa parte di Technologies (€159/mese) e All data (€599/mese). Acquisti uno dei due per filtrare l’elenco completo di 2.273.688 siti, oppure scarichi prima un’anteprima gratuita.
Informazioni su Twitter Emoji (Twemoji)
Pochissimi dei siti registrati per la libreria Twitter Emoji (Twemoji) hanno mai deciso di usarla. Per anni la libreria è stata inclusa in un sistema di gestione dei contenuti molto diffuso come metodo predefinito per visualizzare le emoji, quindi su moltissime pagine il rilevamento è un fatto che riguarda la piattaforma e non chi gestisce il sito. Interpretarlo come una scelta tecnologica deliberata è il principale errore possibile in questo caso.
Il problema che la libreria risolve è concreto. Le emoji native sono disegnate dal sistema operativo, quindi lo stesso carattere appare diverso su un telefono, su un portatile e su un vecchio computer fisso, e a volte non viene visualizzato affatto. La libreria Twitter Emoji (Twemoji) sostituisce le emoji con un set di immagini coerente, in modo che ogni visitatore veda la stessa immagine indipendentemente dal dispositivo. Rilasciato nel 2014 e pubblicato con licenza MIT dall’azienda che oggi si chiama X Corp, il progetto è nato in una piattaforma con un evidente interesse a che le emoji apparissero identiche ovunque i suoi contenuti venissero citati.
A ottobre 2026 la libreria compare su 2.273.688 siti ed è classificata nella categoria Font scripts. Dei siti rilevati, 1.021.779 si trovano negli Stati Uniti, mentre l’estensione .com copre buona parte dei restanti. Una distribuzione con questa forma non dice quasi nulla sulle emoji e parecchio su dove è installata la piattaforma che include la libreria, il che è anche il motivo per cui il dato è utile per qualcosa di diverso dalla tipografia.
Il dato si presta a più di una lettura. La prima è la datazione per coorte. Poiché la libreria è stata distribuita come impostazione predefinita della piattaforma per un determinato arco di anni, è stata poi resa rimovibile e oggi viene comunemente disattivata per ragioni di prestazioni, la sua presenza o assenza permette di collocare approssimativamente il momento in cui la piattaforma di un sito è stata configurata e quanto sia stata messa a punto da allora. Un sito che distribuisce ancora un intero strato di sostituzione delle emoji è un sito che nessuno ha ottimizzato.
La seconda lettura riguarda la proprietà. Il progetto è stato reso open source da un’azienda che nel frattempo ha cambiato proprietario e nome, e i suoi endpoint di distribuzione degli asset sono già stati spostati e ritirati in passato, il che rientra nel normale ciclo di vita di un endpoint di distribuzione gratuito legato a un’azienda che non ha più alcun motivo per finanziarlo. Qualsiasi pagina che carica le immagini da un’origine remota invece di includerle localmente porta con sé una dipendenza da una decisione che non controlla, e questo è un fatto che riguarda la catena di fornitura del software, non il design.
Chi ha bisogno di questa popolazione la vuole intera. I fornitori di soluzioni per le prestazioni vogliono i siti che distribuiscono uno strato di rendering superfluo. Le aziende che si occupano di manutenzione e migrazione vogliono la coorte di piattaforme che la libreria identifica. Chi verifica le richieste verso terze parti vuole ogni pagina che preleva asset da un’origine il cui proprietario l’ha già deprecata una volta. Una ricerca su un singolo dominio non risponde a nessuna di queste domande, perché ciascuna riguarda un gruppo e non un sito, e il gruppo è esattamente ciò che fornisce un file scaricabile, insieme al paese, all’estensione di dominio e alle altre tecnologie registrate per lo stesso host.
I limiti sono ordinari ma reali. I siti che includono gli asset localmente con un nome di file diverso possono sfuggire del tutto al rilevamento, quindi la presenza misurata è una stima per difetto. Il rilevamento non può nemmeno distinguere un’integrazione deliberata da un’impostazione predefinita della piattaforma, ed è esattamente questa la distinzione che un lettore attento deve ricavare dal contesto, osservando cos’altro gira sul sito. Usato come indicatore della generazione della piattaforma, il dato è affidabile. Usato come misura di chi ha scelto consapevolmente una libreria di emoji, sopravvaluterebbe pesantemente l’intenzionalità.
Domande frequenti
Quanti siti web utilizzano Twitter Emoji (Twemoji)?
webatla rileva Twitter Emoji (Twemoji) su 2.3M siti web, aggiornati ogni giorno, ciascuno con il proprio dominio, DNS, WHOIS, IP, paese e ranking.
Posso scaricare l’elenco dei siti web che utilizzano Twitter Emoji (Twemoji)?
Sì, in formato JSONL strutturato. Scarichi prima un campione gratuito.
Che cosa è incluso per ogni sito, e con quale frequenza viene aggiornato?
Dominio, DNS, RDAP/WHOIS, lo stack tecnologico completo, IP e paese, PageRank e Harmonic, ridilevati e riesportati ogni giorno.
Come trovo i siti web che utilizzano Twitter Emoji (Twemoji)?
Acquisti il dataset Technologies, poi scarichi l’elenco completo dei domini in cui rileviamo Twitter Emoji (Twemoji), riesportato ogni giorno.
Che altro contengono i dati sulla tecnologia Twitter Emoji (Twemoji)?
Ogni riga colloca Twitter Emoji (Twemoji) accanto alle altre tecnologie dello stesso sito, oltre a DNS, WHOIS, IP, paese e ranking.
Posso scaricare solo i siti che utilizzano Twitter Emoji (Twemoji), o l’intero database?
Entrambi. Ogni sito che utilizza Twitter Emoji (Twemoji) è incluso nel dataset Technologies, un unico file scaricabile. Oppure acquisti All data per l’intero database: tecnologie, più identità, ranking, DNS e RDAP/WHOIS per ogni dominio, riuniti in un unico file. Esportazione aggiornata ogni giorno.
Come scarico l’elenco dei siti web che utilizzano Twitter Emoji (Twemoji)?
Tre passaggi: (1) scarichi il campione gratuito di 10.000 righe per esaminare lo schema, (2) acquisti il dataset Technologies, (3) scarichi l’elenco completo di tutti i domini in cui rileviamo Twitter Emoji (Twemoji), in un file JSON Lines. Viene riesportato ogni giorno, quindi può riscaricare l’elenco più aggiornato in qualsiasi momento durante il suo periodo di accesso. Ogni riga contiene il dominio, oltre a DNS, WHOIS, IP, paese di hosting e ranking.
Ottenga l’elenco completo dei siti web che usano Twitter Emoji (Twemoji)
Scelga il dataset che copre ciò di cui ha bisogno. Ciascuno include Twitter Emoji (Twemoji) ed è scaricabile in JSONL, ricostruito ogni giorno.
Lo stack tecnologico completo di ogni sito: CMS, pagamenti, analytics, framework.
Tutto quello che abbiamo, in un unico pacchetto. L’universo webatla completo.
Vuole confrontare tutti i dataset fianco a fianco? Visitare la pagina dei prezzi