demo:s3cret
The username and password are joined with a colon before UTF-8 Base64 encoding.
Authorization: Basic ZGVtbzpzM2NyZXQ=Masukkan nama pengguna dan kata sandi untuk menghasilkan header HTTP `Authorization: Basic <base64>` yang siap disalin ke permintaan cURL, Postman, atau konfigurasi Nginx/Apache.
Isi nilai yang diperlukan, tempel teks Anda, atau unggah file yang ingin diproses.
Sebagian besar alat diperbarui secara langsung saat Anda mengetik; beberapa menggunakan satu tombol tindakan.
Salin, unduh, atau bagikan hasil yang dihasilkan — Anda selalu memiliki kendali penuh atas data Anda.
Build the base64-encoded Authorization header value for HTTP Basic Authentication from a username and password.
HTTP Basic Authentication (RFC 7617) sends credentials as "username:password", base64-encoded, inside an Authorization header — Authorization: Basic <encoded value>. Base64 is an encoding, not encryption, so this scheme is only safe to use over HTTPS.
Because base64 is trivially reversible, never send this header over plain HTTP, and avoid Basic Auth entirely for anything sensitive if the API offers a token-based alternative.
Basic base64(username + ":" + password)The username and password are joined with a colon before UTF-8 Base64 encoding.
Authorization: Basic ZGVtbzpzM2NyZXQ=The generated header is just Base64 text for username:password. Treat it like a credential and avoid leaving it visible after copying.
Only when used over HTTPS. The credentials are merely base64-encoded, not encrypted, so anyone who can read the raw request over plain HTTP can recover them instantly.
Yes. The username and password are UTF-8 encoded before being base64-encoded, so any Unicode character is handled correctly.
In the Authorization request header, exactly as generated, e.g. Authorization: Basic dXNlcjpwYXNz.
No. Basic Auth is only Base64-encoded. It should be used over HTTPS and treated like any other credential.
Buat tag meta HTML, Open Graph (Facebook), dan Twitter Card yang optimal.
Hitung rentang subnet CIDR, subnet mask, alamat broadcast, dan host.
Buat URL pelacakan kampanye pemasaran Google Analytics dengan UTM.
Buat aturan robots.txt standar untuk mengontrol perayapan mesin pencari seperti Googlebot.
Validasi struktur dan sintaks file sitemap.xml sesuai standar sitemaps.org.
Identifikasi browser, sistem operasi, versi mesin, dan tipe perangkat.
Cari arti, penyebab, dan solusi kode status HTTP (200, 301, 404, 500).
Cari tipe MIME berdasarkan ekstensi file atau cari ekstensi dari Content-Type.
Konversi nama domain beraksen internasional (IDN) ke format Punycode xn--.
Hitung estimasi durasi unduh atau unggah file berdasarkan ukuran data dan kecepatan internet.