New pages

15:1615:16, 28 January 2026 2026 Round Applicant Guidebook (hist | edit) [479 bytes] Christiane (talk | contribs) (Created page)

05:2405:24, 27 January 2026 MiM Digital Marketing Solution Ltd (hist | edit) [3,721 bytes] Tmsmasum (talk | contribs) (Created page with "{{Organization| |city = Dhaka |country = Bangladesh |date_founded = 2014 |facebook = https://www.facebook.com/bulksms.MiMSMS/ |focus = Digital Marketing, Bulk SMS & Communication Services |founders = Mohammad Masum, Mostafa Kamal |linkedin = https://bd.linkedin.com/company/mim-sms |logo = thumb|alt=MiM SMS|MiMSMS |organization_type = Private Limited Company |website = https://www.mimsms.com |x = codeforhost }} '''MiM Digital Marketing Soluti...")
04:5704:57, 27 January 2026 Alyssa Quinn (hist | edit) [1,625 bytes] Lyssamoo (talk | contribs) (Creating new Person page)

16:4616:46, 23 January 2026 Online Certificate Status Protocol (hist | edit) [6,150 bytes] MarkWD (talk | contribs) (Created page with "'''Online Certificate Status Protocol''' ('''OCSP''') is an IETF protocol for checking the revocation status of an X.509 certificate via an OCSP responder, instead of downloading a full Certificate Revocation List. In the Web PKI, OCSP is intended to help relying parties detect certificates revoked due to compromise or mis-issuance, but its real-world effect depends on client enforcement and responder reachability.<ref name="rfc6960">https://www.rfc-editor.or...")

13:2113:21, 22 January 2026 Certificate Revocation List (hist | edit) [4,606 bytes] MarkWD (talk | contribs) (Created page with "'''Certificate Revocation List''' ('''CRL''') is a signed list published by a Certificate Authority that identifies X.509 certificates revoked before their stated expiration, allowing relying parties (browsers, operating systems, and enterprise clients) to reject certificates that should no longer be trusted.<ref name="rfc5280">[https://datatracker.ietf.org/doc/html/rfc5280 RFC 5280: ''Internet X.509 Public Key Infrastructure Certificate and Certificate Revocatio...")

15:1915:19, 19 January 2026 X.509 (hist | edit) [5,703 bytes] MarkWD (talk | contribs) (Created page with "'''X.509''' is an international standard for public-key certificates and related revocation data structures, most commonly used to support PKI for TLS, secure email, and other authentication and signing systems.<ref name="itu-x509">ITU-T, "Recommendation ITU-T X.509 | ISO/IEC 9594-8 (Public-key and attribute certificate frameworks)." https://www.itu.int/rec/t-rec-x.509</ref> In practice, “X.509 certificate” usually refers to an X.509 version 3 certificate encoded usi...")

03:2603:26, 14 January 2026 Internet Security Research Group (hist | edit) [5,253 bytes] MarkWD (talk | contribs) (Created page with "{{Organization |organization_type = Non-profit |focus = Internet security; Web PKI |date_founded = 2013/05/24 |founders = Josh Aas; Eric Rescorla; J. Alex Halderman; Peter Eckersley |country = United States |city = San Francisco, California |website = https://www.abetterinternet.org/; https://www.isrg.org/ |linkedin = internet-security-research-group |github = abetterinternet }} '''Internet Security Research Group''' ('''ISRG''') is a U.S.-based tax-exempt public-benefi...")

14:3514:35, 9 January 2026 Let’s Encrypt (hist | edit) [5,611 bytes] MarkWD (talk | contribs) (Created page with "'''Let’s Encrypt''' is a free, automated, and open Certification Authority operated by the nonprofit Internet Security Research Group (ISRG).<ref name="le-docs">[https://letsencrypt.org/docs/ Let’s Encrypt Documentation] Retrieved January 9, 2026</ref> It issues publicly-trusted TLS certificates primarily through automated Domain Validation workflows using the Automatic Certificate Management Environment (ACME) protocol. In practice, this significantl...")

13:4713:47, 8 January 2026 Automatic Certificate Management Environment (hist | edit) [5,048 bytes] MarkWD (talk | contribs) (Created page with "'''Automatic Certificate Management Environment''' ('''ACME''') is an IETF standards-track protocol used to automate the issuance, renewal, and revocation of Web PKI certificates by coordinating domain control validation and certificate delivery between a Certification Authority and an automated client.<ref name="rfc8555">[https://www.rfc-editor.org/rfc/rfc8555.html R. Barnes et al., "RFC 8555: Automatic Certificate Management Environment (ACME)", IETF, March 2019.]<...")

13:4813:48, 7 January 2026 Certification Authority (hist | edit) [6,908 bytes] MarkWD (talk | contribs) (Created page with "'''Certification Authority''' ('''CA''') is an organisation that issues and signs X.509 digital certificates used to authenticate domain names and enable encrypted connections on the Web (primarily via TLS and HTTPS). In the context of the Web PKI, a CA’s authority derives less from a formal public mandate than from inclusion in major browser and operating-system trust stores and adherence to ecosystem policy requirements.<ref name="rfc5280">[https://datatracker.ie...")

13:3213:32, 6 January 2026 Web PKI (hist | edit) [10,198 bytes] MarkWD (talk | contribs) (Created page with "'''Web PKI''' ('''Web Public Key Infrastructure''') is the collection of technical mechanisms, certificate authorities, browser and operating-system trust stores, policies, and audit practices that underpin HTTPS and other TLS-based services on the Web. It uses X.509 certificates to bind public keys to DNS-based identifiers (primarily domain names) so that browsers can authenticate web servers and establish encrypted connections.<ref name="wpkops">[https://datatracke...")

11:0011:00, 27 December 2025 Ahlaam Riheel (hist | edit) [2,455 bytes] Ahlaam Riheel (talk | contribs) (Creating new Person page)

05:5205:52, 18 December 2025 Adnan (hist | edit) [144 bytes] Myafternicdomainparking (talk | contribs) (Creating new Event page)

17:4617:46, 16 December 2025 Multicast DNS (hist | edit) [5,316 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 6762.}} '''Multicast DNS''' ('''mDNS''') is a local-link name resolution protocol that reuses the DNS packet format over IP multicast to provide DNS-like queries and responses on networks without a conventional unicast DNS server.<ref name="rfc6762">[https://www.rfc-editor.org/rfc/rfc6762.html S. Cheshire, M. Krochmal, "Multicast DNS", RFC 6762, IETF, February 2013.]</ref><ref name="info6762">[https://www.rfc-editor.or...")

13:1213:12, 15 December 2025 RFC 6762 (hist | edit) [5,673 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For implications on Internet governance, see Multicast DNS.}} '''RFC 6762''', ''Multicast DNS'', is an IETF Standards-Track RFC that specifies how DNS-style queries and responses can be carried over IP multicast on a local link, without requiring any conventional unicast DNS server.<ref name="rfc6762">[https://www.rfc-editor.org/rfc/rfc6762.html S. Cheshire, M. Krochmal, "Multicast DNS", RFC 6762, IETF, February 2013.]</ref> It defines the behaviour commonly...")

13:1413:14, 12 December 2025 .internal (hist | edit) [6,971 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the broader context, see Private Use TLD and Special-Use Domain Names.}} '''.internal''' is a top-level label reserved by ICANN for private-use DNS namespaces that are not part of the global public DNS root. In July 2024, the ICANN Board resolved that <code>.internal</code> will never be delegated in the root zone, so that it can be used by organisations as a non-colliding private-use TLD.<ref name="board2024">[https://www.icann.org/en/board-activ...")

16:4016:40, 11 December 2025 .local (hist | edit) [6,557 bytes] MarkWD (talk | contribs) (Created page with "'''.local''' is a Special-Use Domain Name reserved by the IETF so that it cannot be delegated as a top-level domain in the public [[DNS root. RFC 6762 designates <code>.local.</code> as a link-local namespace for hostnames resolved using Multicast DNS (mDNS) and zero-configuration networking, rather than via conventional unicast DNS.<ref name="rfc6762">[https://www.rfc-editor.org/rfc/rfc6762.html S. Cheshire, M. Krochmal, "Multicast DNS", RFC 6762, IETF, Febr...")

13:2813:28, 10 December 2025 HTTP/3 (hist | edit) [8,351 bytes] MarkWD (talk | contribs) (Created page with "'''HTTP/3''' (RFC 9114) is the third major version of the Hypertext Transfer Protocol, standardised by the IETF as a mapping of HTTP semantics over QUIC rather than TCP.<ref name="rfc9114">[https://www.rfc-editor.org/rfc/rfc9114.html RFC Editor, "RFC 9114: HTTP/3", June 2022.]</ref> It retains the request/response model, methods, and status codes of earlier HTTP versions, but uses QUIC streams, QPACK header compression, and an integrated TLS 1.3 handshake to...")

19:0319:03, 9 December 2025 QUIC (hist | edit) [7,146 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 9000.}} '''QUIC''' (originally "Quick UDP Internet Connections") is a secure transport protocol standardised by the IETF that runs over UDP and integrates transport and cryptographic handshakes into a single layer.<ref name="rfc9000">[https://datatracker.ietf.org/doc/html/rfc9000 J. Iyengar, M. Thomson, "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, IETF, May 2021.]</ref> QUIC underpins HTTP/3 and...")

13:5513:55, 8 December 2025 RFC 9000 (hist | edit) [9,110 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For implications on Internet governance, see QUIC and HTTP/3.}} '''RFC 9000''', ''QUIC: A UDP-Based Multiplexed and Secure Transport'', is an IETF standards-track RFC that defines the core QUIC transport protocol. QUIC provides applications with flow-controlled streams over UDP, enabling secure, multiplexed, low-latency connections with support for connection migration and integrated congestion control. It was published in May 2021 as the main output of t...") originally created as "RC 9000"

17:2017:20, 4 December 2025 Tor (hist | edit) [12,313 bytes] MarkWD (talk | contribs) (Created page with "'''Tor''' ('''The Onion Routing''') is a free and open-source overlay network and software stack that implements onion routing to anonymise low-latency TCP traffic, typically via the Tor Browser, by relaying it through a global network of volunteer-operated relays. It also disposes of its own set of services which use the .onion Special-Use Domain Name. It is developed and maintained by the non-profit Tor Project and is widely used for privacy protection.<ref nam...")
14:1114:11, 4 December 2025 New gTLD Subsequent Procedures Policy Development Process Working Group (hist | edit) [11,592 bytes] Christiane (talk | contribs) (Created page (spliting from the PDP page))

13:4813:48, 3 December 2025 .onion (hist | edit) [6,892 bytes] MarkWD (talk | contribs) (Created page with "'''.onion''' is a Special-Use Domain Name designating Tor onion services. It is not part of the public DNS root, being resolved inside the Tor network rather than via ordinary DNS queries.<ref name="rfc7686">[https://datatracker.ietf.org/doc/html/rfc7686 J. Appelbaum, A. Muffett, "The '.onion' Special-Use Domain Name", RFC 7686, IETF, October 2015.]</ref><ref name="onion-wiki">[https://en.wikipedia.org/wiki/.onion ".onion", Wikipedia (accessed 2025-12-02).]</ref>...")

13:2213:22, 2 December 2025 Special-Use Domain Name (hist | edit) [14,036 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 6761.}} '''Special-Use Domain Names''' are those that Internet protocols treat in a non-standard way, often outside the normal public DNS resolution path. They are recorded in a dedicated IANA registry created by RFC 6761 and are used to avoid ambiguity between the global DNS root and names that are meant for documentation, local networking, privacy-preserving overlays, or alternative naming systems.<ref name="rfc6761"...")

13:1013:10, 1 December 2025 RFC 6761 (hist | edit) [7,114 bytes] MarkWD (talk | contribs) (Created page with "'''RFC 6761''', ''Special-Use Domain Names'', is an IETF standards-track RFC that defines what it means for a domain name to be reserved for "special use", when such reservation is appropriate, and how it is recorded in an IANA registry.<ref name="rfc6761">[https://datatracker.ietf.org/doc/html/rfc6761 S. Cheshire, M. Krochmal, "Special-Use Domain Names", RFC 6761, IETF, February 2013.]</ref><ref name="rfc6761-info">[https://www.rfc-editor.org/info/rfc6761 RFC Editor, "I...")

13:3313:33, 28 November 2025 RFC 9250 (hist | edit) [9,232 bytes] MarkWD (talk | contribs) (Created page with "'''RFC 9250''', ''DNS over Dedicated QUIC Connections'', is an IETF standards-track RFC that specifies DNS over QUIC (DoQ) as a general-purpose encrypted transport for the DNS. It maps DNS queries and responses onto the QUIC transport protocol, aiming to provide privacy properties comparable to DNS over TLS (DoT) and latency characteristics close to classic DNS over UDP.<ref name="rfc9250">[https://datatracker.ietf.org/doc/html/rfc9250 C. Huitema, S. Dickinso...")

17:1217:12, 27 November 2025 DNS over TLS (hist | edit) [7,271 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 7858.}} '''DNS over TLS''' ('''DoT''') is a method of performing DNS resolution over TLS, usually on a dedicated port (853). It encapsulates DNS queries and responses in an encrypted TCP/TLS session between clients and recursive resolvers, with the goal of protecting them from on-path monitoring or tampering while keeping DNS as a distinct protocol layer.<ref name="rfc7858">[https://datatracker.ietf.org/doc/html/rfc785...")

16:3316:33, 26 November 2025 Latin Script Diacritics PDP Working Group (hist | edit) [18,497 bytes] Christiane (talk | contribs) (Created page)
13:5213:52, 26 November 2025 RFC 7858 (hist | edit) [6,711 bytes] MarkWD (talk | contribs) (Created page with "'''RFC 7858''', ''Specification for DNS over Transport Layer Security (TLS)'', is an IETF standards-track RFC that defines '''DNS over TLS''' ('''DoT''') as a way to run DNS over TCP connections in a protected manner.<ref name="rfc7858">[https://datatracker.ietf.org/doc/html/rfc7858 Z. Hu et al., "Specification for DNS over Transport Layer Security (TLS)", RFC 7858, IETF, May 2016.]</ref><ref name="rfcinfo7858">[https://www.rfc-editor.org/info/rfc7858 RFC Editor, "Inform...")

16:1916:19, 25 November 2025 Registration Data Accuracy Scoping Team (hist | edit) [19,532 bytes] Christiane (talk | contribs) (Created page)
15:0315:03, 25 November 2025 DNS over HTTPS (hist | edit) [7,695 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 8484.}} '''DNS over HTTPS''' ('''DoH''') is a method of performing DNS resolution over HTTPS. It encapsulates DNS queries and responses inside encrypted web traffic, aiming to protect them from on-path monitoring or tampering. It integrates the DNS more tightly with the Web application stack.<ref name="rfc8484">[https://datatracker.ietf.org/doc/html/rfc8484 P. Hoffman, P. McManus, "DNS Queries over HTTPS (DoH)", RFC 84...")

16:5216:52, 24 November 2025 GNSO Council Registration Data Accuracy Small Team (hist | edit) [12,873 bytes] Christiane (talk | contribs) (Created page)
12:2612:26, 24 November 2025 RFC 8484 (hist | edit) [5,675 bytes] MarkWD (talk | contribs) (Created page with "'''RFC 8484''', ''DNS Queries over HTTPS (DoH)'', is an IETF standards-track RFC that specifies how standard DNS queries and responses can be carried over HTTPS.<ref name="rfc8484">[https://datatracker.ietf.org/doc/html/rfc8484 P. Hoffman, P. McManus, "DNS Queries over HTTPS (DoH)", RFC 8484, IETF, October 2018.]</ref> Each DNS query–response pair is mapped to a single HTTP exchange, allowing DNS traffic to use the same encrypted transport as Web applications.<ref name...")

18:0318:03, 21 November 2025 Board Readiness Small Team (hist | edit) [2,916 bytes] Christiane (talk | contribs) (Created page)
16:0316:03, 21 November 2025 CGNAT (hist | edit) [6,277 bytes] MarkWD (talk | contribs) (Created page with "{{Note|For the technical specification, see RFC 6598.}} '''Carrier-grade NAT''' ('''CGNAT''' or '''CGN''') is a large-scale NAT technique used by ISPs to let many subscribers share the same pool of public IPv4 addresses. It emerged as a response to IPv4 address exhaustion and is closely linked to the allocation of the "100.64.0.0/10" shared address space for use inside provider networks.<ref>[https://datatracker.ietf.org/doc/html/rfc6598 J. Weil et al., "IANA-Reserv...")

15:2315:23, 20 November 2025 RFC 6598 (hist | edit) [3,274 bytes] MarkWD (talk | contribs) (Creating new Norm page) Tags: Mobile edit Mobile web edit Advanced mobile edit

15:0915:09, 17 November 2025 Blue Water Law (hist | edit) [640 bytes] Christiane (talk | contribs) (Created page)
14:1314:13, 17 November 2025 Phil Lodico (hist | edit) [435 bytes] Christiane (talk | contribs) (Created page) Tag: Visual edit
14:0614:06, 17 November 2025 Josh Bourne (hist | edit) [324 bytes] Christiane (talk | contribs) (Created page) Tag: Visual edit: Switched

13:5613:56, 13 November 2025 Alessandro Baruffi (hist | edit) [1,512 bytes] Anddreyinsarov (talk | contribs) (Creation of the page)

15:2115:21, 12 November 2025 CCATLAT (hist | edit) [1,364 bytes] MarkWD (talk | contribs) (Created page with "{{Organization |logo = |organization_type = Non-profit |focus = Internet Governance; ICT training |date_founded = 1987 |founders = Oscar Messano |ownership = |country = Argentina; Uruguay |city = Buenos Aires; Montevideo |subsidiaries = |website = https://ccatlat.org }} '''Centro de Capacitación en Alta Tecnología para Latinoamérica y el Caribe''' ('''CCATLAT''') is a non-profit training center founded in 1987 that delivers ICT and Internet Governance programs acr...")

13:2613:26, 11 November 2025 Rec 6 CWG-Morality and Public Order (hist | edit) [5,058 bytes] Christiane (talk | contribs) (Created page)

15:0515:05, 10 November 2025 Middle East and Adjoining Countries Strategy Working Group (hist | edit) [6,746 bytes] Christiane (talk | contribs) (Created page)

15:3015:30, 4 November 2025 Evandro Varonil (hist | edit) [3,025 bytes] Evandrovaronil (talk | contribs) (Created page with "{{People|portrait=|organization=LACNIC, ABRINT, SEINESP, LAC-ISP|job title=Internet and Telecommunications Executive|region=Latin America and Caribbean|country=Brazil|stakeholdergroup=ISPs|email=|website=|linkedin=https://www.linkedin.com/in/evandrovaronil}} '''Evandro Varonil''' is a Brazilian Internet and telecommunications executive, currently serving as a '''Director of Internet Service Providers (ISPs)''' in Brazil. He is the '''Vice-President of LACNIC''' (In...") Tag: Visual edit

28 January 2026

27 January 2026

23 January 2026

22 January 2026

19 January 2026

14 January 2026

9 January 2026

8 January 2026

7 January 2026

6 January 2026

27 December 2025

18 December 2025

16 December 2025

15 December 2025

12 December 2025

11 December 2025

10 December 2025

9 December 2025

8 December 2025

4 December 2025

3 December 2025

2 December 2025

1 December 2025

28 November 2025

27 November 2025

26 November 2025

25 November 2025

24 November 2025

21 November 2025

20 November 2025

17 November 2025

13 November 2025

12 November 2025

11 November 2025

10 November 2025

4 November 2025