Referensi Skema URI
Jelajahi referensi lengkap lebih dari 60 skema URI yang diorganisasi per kategori. Setiap entri mencakup spesifikasi format skema, contoh penggunaan dunia nyata, referensi RFC, port standar, dan status registrasi IANA. Cari, filter per kategori, dan salin nama skema, format, serta contoh dengan satu klik — semua data bersifat lokal, tanpa perlu server.
Browse and search a comprehensive reference of over 60 URI schemes organized by category. Each entry includes format specifications, usage examples, RFC references, and IANA registration status - perfect for developers, technical writers, and students.
66 schemes
🌐Web & Internet(4 schemes)
httpHypertext Transfer Protocol - the foundation of data communication on the World Wide Web. Used for transferring HTML pages, API responses, images, and other web resources over TCP/IP.
Format
http://host[:port]/path[?query][#fragment]Example
http://example.com/index.html?page=1#section80IANA: RegisteredRFC: RFC 7230, RFC 7540 (HTTP/2), RFC 9116httpsHypertext Transfer Protocol Secure - HTTP over TLS/SSL encryption. Provides authenticated and encrypted communication between clients and servers, protecting against eavesdropping and tampering.
Format
https://host[:port]/path[?query][#fragment]Example
https://www.example.com/secure-page443IANA: RegisteredRFC: RFC 2818, RFC 7230wsWebSocket - provides full-duplex communication channels over a single TCP connection. Used for real-time applications like chat, gaming, live feeds, and collaborative editing.
Format
ws://host[:port]/pathExample
ws://echo.websocket.org/chat80IANA: RegisteredRFC: RFC 6455wssWebSocket Secure - WebSocket over TLS/SSL. Provides encrypted WebSocket connections for secure real-time communication.
Format
wss://host[:port]/pathExample
wss://api.example.com/ws/events443IANA: RegisteredRFC: RFC 6455🔌Network & Communication(14 schemes)
ftpFile Transfer Protocol - standard network protocol for transferring files between a client and server over TCP/IP. Supports authenticated and anonymous access with separate control and data connections.
Format
ftp://[user[:password]@]host[:port]/pathExample
ftp://ftp.example.com/pub/files/readme.txt21IANA: RegisteredRFC: RFC 959, RFC 1738ftpsFTP over SSL/TLS - FTP encrypted with TLS/SSL for secure file transfers. Adds encryption to standard FTP to protect credentials and data in transit.
Format
ftps://host[:port]/pathExample
ftps://secure.example.com/files/report.pdf990IANA: RegisteredRFC: RFC 4217sftpSSH File Transfer Protocol - file transfer over SSH (Secure Shell). Provides secure file operations including transfer, access, and management over an encrypted SSH connection.
Format
sftp://[user@]host[:port]/pathExample
sftp://[email protected]/home/user/document.txt22IANA: RegisteredRFC: SSH File Transfer Protocol (draft)sshSecure Shell - cryptographic network protocol for secure remote login, command execution, and other secure network services over an unsecured network.
Format
ssh://[user@]host[:port]Example
ssh://[email protected]:222222IANA: RegisteredRFC: RFC 4251, RFC 4252telnetTelnet - bidirectional interactive text-oriented communication protocol using virtual terminal connections. Largely superseded by SSH due to lack of encryption.
Format
telnet://host[:port]Example
telnet://rainmaker.wunderground.com23IANA: RegisteredRFC: RFC 854, RFC 1738ldapLightweight Directory Access Protocol - open protocol for accessing and maintaining distributed directory information services over IP networks. Used for authentication and directory lookups.
Format
ldap://host[:port]/dn[?attributes][?scope][?filter]Example
ldap://ldap.example.com/cn=John%20Doe,dc=example,dc=com389IANA: RegisteredRFC: RFC 4516ldapsLDAP over SSL - secure version of LDAP that uses TLS/SSL encryption for directory access and authentication.
Format
ldaps://host[:port]/dnExample
ldaps://secure-ldap.example.com/636IANA: RegisteredRFC: RFC 4513imapInternet Message Access Protocol - email protocol for accessing and managing messages on a mail server. Allows clients to organize, search, and synchronize email across multiple devices.
Format
imap://[user[:password]@]host[:port]/mailboxExample
imap://[email protected]/INBOX143IANA: RegisteredRFC: RFC 3501, RFC 5092imapsIMAP over SSL/TLS - encrypted IMAP for secure email access. Protects credentials and email content during transmission.
Format
imaps://[user[:password]@]host[:port]/mailboxExample
imaps://[email protected]/INBOX993IANA: RegisteredRFC: RFC 3501, RFC 8314pop3Post Office Protocol version 3 - email protocol used by local email clients to retrieve email from a remote server. Typically downloads and optionally deletes messages from the server.
Format
pop3://[user[:password]@]host[:port]Example
pop3://[email protected]/110IANA: RegisteredRFC: RFC 1939, RFC 2384pop3sPOP3 over SSL/TLS - encrypted POP3 for secure email retrieval. Protects credentials during download.
Format
pop3s://[user[:password]@]host[:port]Example
pop3s://[email protected]/995IANA: RegisteredRFC: RFC 1939, RFC 8314nntpNetwork News Transfer Protocol - protocol for distributing, querying, posting, and retrieving Usenet articles (newsgroup messages).
Format
nntp://host[:port]/newsgroup[/article-number]Example
nntp://news.example.com/comp.lang.javascript119IANA: RegisteredRFC: RFC 3977ircInternet Relay Chat - protocol for real-time text messaging and group communication in chat channels. Used for community discussions, support channels, and collaborative communication.
Format
irc://host[:port]/channel[?key=password]Example
irc://irc.libera.chat/#ubuntu6667IANA: RegisteredRFC: RFC 2812ircsIRC over SSL/TLS - encrypted IRC for secure chat communication. Protects messages and authentication from eavesdropping.
Format
ircs://host[:port]/channelExample
ircs://irc.libera.chat:6697/#security6697IANA: RegisteredRFC: RFC 2812✉️Email & Messaging(5 schemes)
mailtoEmail address - opens the default email client with pre-filled recipient, subject, and body. Used for creating email links on web pages.
Format
mailto:address[?subject=...][&cc=...][&bcc=...][&body=...]Example
mailto:[email protected]?subject=Hello&body=Hi%20thereRFC 6068smsShort Message Service - opens the default messaging application with a pre-filled recipient number and message body. Used for mobile SMS links.
Format
sms:phone-number[?body=message]Example
sms:+1234567890?body=Hello%20from%20the%20websiteRFC 5724telTelephone number - initiates a call to the specified phone number on devices with telephony capabilities. Widely supported on mobile devices.
Format
tel:phone-numberExample
tel:+1-800-555-0199RFC 3966faxFacsimile - specifies a fax number for sending documents via fax. Less commonly used with the rise of digital document sharing.
Format
fax:phone-numberExample
fax:+1-800-555-0200RFC 2806xmppExtensible Messaging and Presence Protocol - open protocol for instant messaging, presence information, and contact list maintenance. Used by Jabber and many chat applications.
Format
xmpp:jid[/resource]Example
xmpp:[email protected]RFC 5122, RFC 7622📦Data & Resources(5 schemes)
dataData URI - allows embedding small data items directly in a URI as base64-encoded or percent-encoded content. Commonly used for embedding images, fonts, and CSS in web pages to reduce HTTP requests.
Format
data:[<mediatype>][;base64],<data>Example
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA...RFC 2397blobBinary Large Object - used to represent binary data held in the browser's Blob or File API. Creates object URLs for files, images, and other binary data generated client-side.
Format
blob:origin/uuidExample
blob:https://example.com/550e8400-e29b-41d4-a716-446655440000File API (W3C)aboutAbout - used internally by browsers to display built-in pages. Examples include about:blank (empty page), about:config (Firefox settings), and about:debugging (browser internals).
Format
about:[page]Example
about:blankHTML StandardjavascriptJavaScript - executes JavaScript code when used as a URL in a browser. Typically used in bookmarklets and onclick handlers. Considered a security risk in modern web development.
Format
javascript:codeExample
javascript:alert('Hello, world!')HTML StandardgeoGeographic Location - specifies a geographic location by coordinates (latitude and longitude). Opens the device's mapping application at the specified location.
Format
geo:lat,lon[?z=zoom]Example
geo:48.8584,2.2945?z=15RFC 5870📁Files & Storage(4 schemes)
fileLocal File - references a file on the local filesystem. Used by browsers and applications to access local resources. Security restrictions apply in browser contexts.
Format
file://[host]/pathExample
file:///home/user/document.pdfRFC 1738smbServer Message Block - network file sharing protocol used by Windows systems for accessing shared files, printers, and other network resources on local networks.
Format
smb://host/share/pathExample
smb://server/shared-folder/document.docx445IANA: RegisteredRFC: Microsoft specificationdavWebDAV (Web Distributed Authoring and Versioning) - extends HTTP for collaborative file management, allowing clients to remotely create, move, delete, and edit files on a web server.
Format
dav://host[:port]/pathExample
dav://webdav.example.com/shared-documents/RFC 4918davsWebDAV over HTTPS - secure WebDAV using TLS/SSL encryption for authenticated remote file management.
Format
davs://host[:port]/pathExample
davs://secure-webdav.example.com/443IANA: RegisteredRFC: RFC 4918🎬Media & Content(5 schemes)
magnetMagnet URI - used by peer-to-peer file sharing networks (especially BitTorrent) to identify files by content hash rather than location. Enables decentralized file downloads without a central server.
Format
magnet:?xt=urn:...params...Example
magnet:?xt=urn:btih:54a6f8f7a6d8e7f9a0b1c2d3e4f5a6b7c8d9e0f&dn=ubuntu-22.04.isoRFC 8157bitcoinBitcoin - used for Bitcoin payment requests. Specifies the recipient address, amount, label, and message for cryptocurrency transactions.
Format
bitcoin:address[?amount=...][&label=...][&message=...]Example
bitcoin:1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa?amount=0.001&label=DonationBIP 21mmsMicrosoft Media Server - proprietary protocol for streaming multimedia content from Windows Media Services. Used for audio and video streaming in legacy Windows Media applications.
Format
mms://host[:port]/pathExample
mms://media.example.com/streaming/video.wmv1755IANA: RegisteredRFC: Microsoft specificationrtspReal-Time Streaming Protocol - network protocol for controlling streaming media servers. Used for establishing and controlling media sessions between endpoints for video and audio streaming.
Format
rtsp://host[:port]/pathExample
rtsp://media.example.com:554/stream/live554IANA: RegisteredRFC: RFC 7820, RFC 7821aptAdvanced Package Tool - used on Debian-based Linux systems to install, update, and manage software packages from repositories. Opens the package manager to install the specified package.
Format
apt:package-nameExample
apt:firefoxDebian specification🛠️Developer & Tools(16 schemes)
gitGit version control - references a Git repository for cloning, fetching, or pulling source code. Supports various transport protocols including SSH, HTTPS, and local paths.
Format
git://host[:port]/pathExample
git://github.com/user/repository.git9418IANA: RegisteredRFC: Git documentationsvnSubversion - references a Subversion (SVN) repository for version control operations. Used for checking out, committing, and updating source code.
Format
svn://host[:port]/path[/revision]Example
svn://svn.example.com/repos/project/trunk3690IANA: RegisteredRFC: SVN documentationdockerDocker - references Docker images and registries for container management. Used to pull and run container images from Docker registries.
Format
docker://[registry/]image[:tag]Example
docker://docker.io/library/nginx:latestDocker documentationnpmNode Package Manager - references packages in the npm registry for JavaScript/Node.js package management. Opens the package page or triggers installation.
Format
npm:package-name[@version]Example
npm:lodashnpm documentationandroid-appAndroid App - deep links into specific Android applications. Directly opens a designated app or activity, enabling seamless app-to-app navigation on Android devices.
Format
android-app://package-name/scheme/host/pathExample
android-app://com.example.app/http/example.com/product/123Android documentationios-appiOS App - deep links into specific iOS applications using Apple's Universal Links. Opens a native app from a web link if the app is installed.
Format
ios-app://app-store-id/url-pathExample
ios-app://1234567890/example.com/product/123Apple documentationintentAndroid Intent - triggers Android's intent system to perform an action. Used for deep linking, sharing, and inter-app communication on Android.
Format
intent://host/path#Intent;params;endExample
intent://example.com#Intent;scheme=https;endAndroid documentationms-settingsWindows Settings - opens specific settings pages in Windows 10 and 11. Used for deep-linking to accessibility, network, display, and other system settings panels.
Format
ms-settings:[page-name]Example
ms-settings:network-wifiMicrosoft documentationchromeChrome Browser - used internally by the Chromium browser to access browser-specific pages, extensions, and developer tools.
Format
chrome://[page[/subpage]]Example
chrome://settings/securityChromium documentationedgeEdge Browser - used internally by Microsoft Edge to access browser-specific settings, extensions, and management pages.
Format
edge://[page[/subpage]]Example
edge://settings/privacyMicrosoft documentationredisRedis - connects to a Redis key-value store database server. Used in connection strings for Redis clients and database management tools.
Format
redis://[:password@]host[:port][/db]Example
redis://user:password@localhost:6379/06379IANA: RegisteredRFC: Redis documentationpostgresqlPostgreSQL - connects to a PostgreSQL database server. Used in connection strings for database clients, ORMs, and management tools.
Format
postgresql://[user[:password]@]host[:port]/database[?params]Example
postgresql://user:password@localhost:5432/mydb5432IANA: RegisteredRFC: PostgreSQL documentationmongodbMongoDB - connects to a MongoDB database server. Used in connection strings for MongoDB drivers, ORMs, and database administration tools.
Format
mongodb://[user:password@]host[:port]/database[?params]Example
mongodb://admin:password@localhost:27017/mydb27017IANA: UnregisteredRFC: MongoDB documentationmysqlMySQL - connects to a MySQL database server. Used in connection strings for MySQL clients, applications, and database management.
Format
mysql://[user:password@]host[:port]/database[?params]Example
mysql://user:password@localhost:3306/mydb3306IANA: UnregisteredRFC: MySQL documentationrdpRemote Desktop Protocol - Microsoft's proprietary protocol for remote desktop connections to Windows computers. Provides graphical remote access with encryption.
Format
rdp://host[:port]Example
rdp://remote-worksation.example.com:33893389IANA: UnregisteredRFC: Microsoft specificationvncVirtual Network Computing - platform-independent protocol for remote graphical desktop sharing. Allows remote control of another computer's desktop interface.
Format
vnc://host[:port]Example
vnc://server.example.com:59015900IANA: RegisteredRFC: RFC 6143💳Commerce & Payments(3 schemes)
paytoPayment Pointer - standard URI for initiating payments across different payment systems. Designed as a universal payment initiation scheme for the Web.
Format
payto://payment-system/account[?amount=...][&message=...]Example
payto://iban/DE89370400440532013000?amount=100.00RFC 8905venmoVenmo - initiates a Venmo payment or request to another Venmo user. Opens the Venmo app with pre-filled payment details.
Format
venmo://...params...Example
venmo://paycharge?txn=pay&recipients=JohnDoe&amount=25.00¬e=ThanksVenmo documentationethereumEthereum - initiates cryptocurrency transactions or interactions with the Ethereum blockchain. Supports sending ETH, tokens, and executing smart contract functions.
Format
ethereum:address[@chain-id][?value=...][&gas=...]Example
ethereum:0x742d35Cc6634C0532925a3b844Bc1e9Fb2D9A5a0?value=1.0EIP-681💻Operating System(5 schemes)
itmsiTunes Store - links to content in the Apple iTunes Store, App Store, and Apple Books. Opens the appropriate Apple store application to view music, apps, books, or podcasts.
Format
itms://app/app-name/id[app-id]Example
itms://itunes.apple.com/app/example/id123456789Apple documentationitms-appsiTunes Apps - specifically targets the iOS App Store to open a particular application page for download or review.
Format
itms-apps://apps.apple.com/app/[name]/id[app-id]Example
itms-apps://apps.apple.com/app/example/id123456789Apple documentationmarketGoogle Play Store - opens the Google Play Store to a specific application or search result. Used on Android devices for app discovery and installation.
Format
market://details?id=package-nameExample
market://details?id=com.example.appAndroid documentationsteamSteam - opens the Steam gaming platform to a specific game, store page, or community feature. Used for deep-linking to Steam content.
Format
steam://action/parametersExample
steam://store/730Steam documentationfacetimeFaceTime - initiates a FaceTime audio or video call with the specified contact on Apple devices.
Format
facetime://[email|phone-number]Example
facetime://[email protected]Apple documentation📜Historical(5 schemes)
gopherGopher - early internet protocol for distributing, searching, and retrieving documents. Predecessor to the World Wide Web, now largely obsolete but still supported by some legacy systems.
Format
gopher://host[:port]/[type]pathExample
gopher://gopher.example.com/1/dir/file.txt70IANA: RegisteredRFC: RFC 1436, RFC 4266waisWide Area Information Server - early internet search protocol for searching indexed databases. Predates modern web search engines and is now obsolete.
Format
wais://host[:port]/databaseExample
wais://wais.example.com/mydatabaseRFC 1625, RFC 1738prosperoProspero - distributed directory service protocol developed at the University of Washington. An early system for organising and accessing distributed resources, now obsolete.
Format
prospero://host[:port]/pathExample
prospero://prospero.example.com/dir/fileRFC 1738cidContent Identifier - used in email MIME (Multipurpose Internet Mail Extensions) to reference embedded content within a multipart email message. Used with the Content-ID header.
Format
cid:content-idExample
RFC 2392midMessage Identifier - used to reference email messages by their Message-ID header. Allows referencing specific email messages in a mailstore.
Format
mid:message-idExample
mid:<[email protected]>RFC 2392Mengapa menggunakan Referensi Skema URI kami?
- Basis data skema yang lengkap: jelajahi lebih dari 60 skema URI yang diorganisasi ke 10 kategori — dari protokol web (http, https) dan standar jaringan (ftp, ssh, irc) hingga skema aplikasi modern (android-app, ios-app) dan format historis (gopher, wais).
- Pencarian & filter cerdas: cari skema berdasarkan nama, deskripsi, atau kategori. Filter berdasarkan status (permanen, sementara, historis, tidak resmi) atau jelajahi berdasarkan kelompok kategori. Antarmuka interaktifnya memudahkan menemukan skema yang Anda butuhkan.
- Informasi skema yang rinci: setiap entri mencakup deskripsi lengkap, spesifikasi format penggunaan, contoh URI nyata, nomor referensi RFC, port standar (bila ada), dan status registrasi IANA — semuanya di satu tempat.
- Salin & rujuk dengan satu klik: salin nama skema, contoh URI, atau pola format apa pun dengan satu klik. Sempurna untuk pengembang yang menulis dokumentasi, mengonfigurasi aplikasi, atau mempelajari standar URI.
Kasus penggunaan umum Referensi Skema URI
- Pengembangan & integrasi web: saat membangun aplikasi web yang perlu menangani berbagai skema URI — dari tautan mailto dan nomor tel: hingga deep linking dengan skema android-app dan ios-app — cari cepat format, parameter, dan contoh penggunaan yang benar.
- Mempelajari standar URI: pelajar dan pengembang yang mempelajari protokol internet dapat menelusuri daftar lengkap skema URI terdaftar IANA, memahami sejarahnya, dan melihat contoh penggunaan nyata dengan referensi RFC untuk studi lebih dalam.
- Konfigurasi API & layanan: saat mengonfigurasi string koneksi database, URL message queue, atau endpoint layanan, rujuk format skema yang benar untuk PostgreSQL, Redis, MongoDB, MySQL, dan layanan umum lain — beserta nomor port dan format autentikasi.
- Dokumentasi & penulisan teknis: penulis teknis dapat merujuk format skema URI yang benar, contoh, dan nomor RFC saat menulis dokumentasi pengembang, panduan API, dan manual konfigurasi — memastikan akurasi di seluruh dokumentasi.
- Audit & analisis keamanan: profesional keamanan dapat cepat mencari tujuan dan perilaku berbagai skema URI saat menganalisis email phishing, tautan berbahaya, atau handler URI mencurigakan. Pahami skema mana yang dapat menjalankan kode atau mengakses sumber daya sistem.
- Deep linking lintas platform: pengembang mobile dan desktop yang menerapkan deep linking dapat merujuk format URI yang benar untuk Android (intent://, android-app://), iOS (ios-app://), Windows (ms-settings://), dan skema khusus platform lainnya.
Apa itu skema URI?
Skema URI adalah komponen pertama dari Uniform Resource Identifier (URI) yang mengidentifikasi protokol atau mekanisme untuk mengakses sumber daya. Skema diikuti tanda titik dua (:) dan jalur spesifik skema. Misalnya, pada https://example.com, skemanya adalah https. Skema didaftarkan ke IANA (Internet Assigned Numbers Authority) dan dapat berupa standar permanen, proposal sementara, atau konvensi tidak resmi yang dipakai aplikasi dan platform tertentu.
URI vs URL vs URN
URI (Uniform Resource Identifier) adalah kategori terluas — string apa pun yang mengidentifikasi sumber daya. URL (Uniform Resource Locator) adalah URI yang juga menyediakan cara menemukan sumber daya (seperti http://). URN (Uniform Resource Name) adalah URI yang menamai sumber daya tetapi tidak menentukan cara mengaksesnya (seperti urn:isbn:0451450523). Semua URL adalah URI, tetapi tidak semua URI adalah URL. Sebagian besar skema dalam referensi ini adalah skema URL karena memberi informasi lokasi.
Status skema dijelaskan
Skema URI diklasifikasikan berdasarkan status registrasinya di IANA. Skema permanen telah terstandardisasi penuh melalui proses RFC dan diadopsi luas. Skema sementara telah diajukan ke IANA tetapi mungkin belum sepenuhnya terstandardisasi. Skema historis dulu dipakai tetapi kini usang (seperti gopher dan wais). Skema tidak resmi adalah konvensi yang banyak dipakai (seperti docker://, npm:, market://) yang belum terdaftar secara formal di IANA.
Privasi & keamanan
Ini adalah alat referensi — semua data skema disimpan lokal di browser Anda. Tidak ada data yang diunggah ke server, dan tidak ada permintaan jaringan saat menjelajahi daftar skema. Alat ini tidak memerlukan pendaftaran atau kunci API dan berfungsi sepenuhnya offline setelah pemuatan halaman pertama. Gunakan dengan bebas untuk mempelajari skema URI, merujuk format untuk dokumentasi, atau memverifikasi sintaks URI untuk aplikasi Anda.
Pertanyaan yang Sering Diajukan
Skema URI mengidentifikasi mekanisme untuk mengakses sumber daya (seperti «https» untuk konten web, «mailto» untuk alamat email). Protokol adalah kumpulan aturan sebenarnya yang mengatur komunikasi (seperti HTTP/2, SMTP). Meskipun banyak skema URI bersesuaian dengan protokol, beberapa seperti «mailto» tidak terikat pada protokol jaringan tertentu.
IANA (Internet Assigned Numbers Authority) memelihara registri resmi skema URI. Registrasi IANA berarti skema telah didokumentasikan, ditinjau, dan ditambahkan ke jalur standar secara formal. Skema yang terdaftar menjamin interoperabilitas dan mencegah konflik penamaan. Namun, banyak skema yang banyak dipakai (seperti docker://, npm:, market://) tidak terdaftar di IANA tetapi menjadi standar de facto.
Referensi ini mengelompokkan skema ke 10 kategori fungsional: Web & Internet (http, https, ws), Jaringan & Komunikasi (ftp, ssh, irc), Email & Pesan (mailto, sms, tel), Data & Sumber Daya (data, blob, geo), File & Penyimpanan (file, smb, dav), Media & Konten (magnet, rtsp), Pengembangan & Alat (git, docker, redis), Perdagangan & Pembayaran (payto, ethereum), Sistem Operasi (itms, market, steam), dan Historis (gopher, wais).
Bisa, aplikasi dapat mendefinisikan skema URI kustom untuk keperluannya sendiri (seperti myapp://action). Di banyak platform, aplikasi dapat mendaftar untuk menangani skema kustom. Untuk interoperabilitas luas, Anda sebaiknya mendaftarkan skema ke IANA melalui proses RFC. Untuk penggunaan privat atau perusahaan, skema kustom tanpa registrasi umum dipakai tetapi bisa berkonflik dengan aplikasi lain yang memakai nama yang sama.
https adalah skema URI yang paling luas dipakai di internet modern, mencakup sebagian besar lalu lintas web. Skema lain yang sangat umum meliputi http, mailto (ada di mana-mana pada tautan email), sms dan tel (banyak dipakai di perangkat seluler), dan data (dipakai untuk menyematkan sumber daya di halaman web dan mengurangi permintaan HTTP).
Browser modern menangani skema web umum secara native (http, https, data, blob, about, javascript). Beberapa skema memicu aplikasi eksternal (mailto membuka klien email, tel memulai panggilan). Skema lain mungkin memerlukan instalasi perangkat lunak tertentu atau tidak didukung di konteks browser. Skema khusus platform hanya berfungsi di sistem operasi masing-masing.
Status historis menunjukkan bahwa skema URI pernah aktif dipakai tetapi kini dianggap usang atau digantikan standar yang lebih baru. Misalnya, gopher adalah protokol konten awal sebelum web, dan telnet sebagian besar digantikan SSH karena alasan keamanan. Skema ini dipelihara untuk tujuan arsip dan edukasi.
Bagi pengembang, informasi paling berguna adalah spesifikasi format dan contoh URI setiap skema. Gunakan keduanya untuk menyusun URI dengan benar di kode, mengonfigurasi string koneksi database (postgresql://, redis://), menyiapkan deep linking (android-app://, ios-app://), atau menangani integrasi skema pihak ketiga. Referensi RFC memberi spesifikasi lengkap untuk implementasi yang sesuai standar.
Ya, Referensi Skema URI sepenuhnya gratis. Semua data skema disimpan lokal di browser Anda — tidak ada data yang diunggah ke server, tidak perlu kunci API, dan tidak perlu pendaftaran. Jelajahi, cari, dan rujuk skema URI sebanyak yang Anda butuh, sepenuhnya offline dan dengan privasi penuh.