Your Permanent Account Number is your financial identity in India. Download your e-PAN in PDF format in under a minute through NSDL (Protean) or UTIITSL — the two official government-authorized portals.
Enter PAN number and download
Everything you need to know about India's most important tax document — explained simply.
PAN stands for Permanent Account Number. It's a 10-character code — letters and numbers mixed — that the Income Tax Department gives you. It stays the same for your entire life. No expiry, no renewal needed.
Think of it as your financial fingerprint. Every major money transaction you do — salary, rent, investments, property — gets linked to this one number. It tells the government who paid what and to whom.
Indian residents can apply for a PAN online through UTIITSL or NSDL. The process takes 10–15 minutes. You'll need your Aadhaar, a passport-size photo, and basic personal details.
If your Aadhaar is already linked to your mobile number, you can get an Instant e-PAN completely free through the Income Tax Department portal. The e-PAN is issued within minutes using OTP verification — no paperwork needed.
If you're a foreign national or NRI earning any income from India — rent, dividends, capital gains, salary — you need a PAN. Without it, TDS is cut at the highest rate (30%+), even if your actual tax liability is lower.
Foreign citizens apply using Form 49AA. You'll need a copy of your passport, valid visa, and overseas address proof. The physical card takes 15–20 working days. The Instant e-PAN option is only available for Aadhaar holders.
Four simple steps. Done in under 5 minutes.
Type your 10-character PAN in the box at the top of this page. It looks like ABCDE1234F.
Click "Download via NSDL" or "Download via UTIITSL". Both are official. Either works fine.
On the government portal, verify using your Aadhaar OTP or date of birth as required.
Your e-PAN PDF will be ready. Password is your date of birth in DDMMYYYY format.
The TFTP server is a perfect example of "worse is better" in protocol design. It does almost nothing — but it does that nothing reliably, with minimal code, and runs on practically any networked device.
You wouldn’t use TFTP to share family photos or deploy a web app. But when you need to wake up a bare-metal server, flash a router, or provision 500 desk phones, TFTP remains the simplest tool for the job.
Just remember: Put it behind a firewall, never expose it to the internet, and use it only where simplicity outweighs security.
Have a TFTP war story or a clever use case? Share it in the comments below.
A TFTP (Trivial File Transfer Protocol) Server is a simple server used to transfer files between network devices, most commonly for booting diskless workstations or backing up configurations for network equipment like routers and switches. Key Characteristics Trivial Transfers with TFTP, Part 3: Usage - Linux.com
The Essential Guide to TFTP Servers: Simplicity in Data Transfer
In the world of networking, where complex protocols like HTTPS and SFTP dominate the conversation, there remains a quiet, indispensable workhorse that has survived since the early 1980s: the TFTP (Trivial File Transfer Protocol) Server.
While it lacks the bells and whistles of modern protocols, its simplicity is exactly what makes it a critical tool for network administrators, embedded systems developers, and IT professionals. What is a TFTP Server?
A TFTP Server is a device or software application that uses the Trivial File Transfer Protocol (defined in RFC 1350) to send and receive files. Unlike FTP, which uses the robust TCP protocol, TFTP operates over UDP (User Datagram Protocol), specifically on port 69.
Because it is "trivial," the protocol has a very small footprint. It doesn’t support directory listing, user authentication, or file deletion. It simply does two things: Read Request (RRQ) and Write Request (WRQ). How It Works: The Bare Bones of Transfer TFTP Server
TFTP works on a stop-and-wait mechanism. Here is the simplified flow:
The Request: The client sends a request to the server to either get or put a file.
Data Blocks: The server sends the file in fixed-size blocks (usually 512 bytes).
Acknowledgment: For every block sent, the receiver must send back an "Acknowledgment" (ACK) packet.
Completion: The transfer ends when a block arrives that is smaller than the standard 512 bytes.
Because UDP is "connectionless," TFTP handles its own error recovery. If an ACK doesn’t arrive within a certain timeframe, the server simply re-sends the last block. Key Use Cases: Why We Still Use It
You might wonder why anyone would use a protocol without passwords or encryption. The answer lies in resource-constrained environments. 1. Booting Diskless Workstations (PXE)
The most common use for TFTP today is Preboot Execution Environment (PXE). When a computer or server boots up without an operating system on its hard drive, the BIOS/UEFI uses TFTP to download a small bootloader or OS image from the network. 2. Configuring Network Hardware
Routers, switches, and firewalls (from giants like Cisco and Juniper) often use TFTP to back up or restore configuration files and update firmware. It’s lightweight enough to fit into the tiny firmware chips of these devices. 3. VoIP Phone Provisioning The TFTP server is a perfect example of
When you plug in an IP phone, it often reaches out to a TFTP server to download its specific configuration settings, wallpaper, and firmware updates. Pros and Cons of TFTP The Advantages:
Minimal Footprint: The code required to implement a TFTP client is tiny, making it perfect for boot ROMs.
Easy Configuration: Most TFTP servers can be set up in under 60 seconds.
No Overhead: Without the "handshaking" of TCP or the encryption of SFTP, it is very fast on low-latency local networks. The Disadvantages:
Security Risk: There is zero encryption. Anyone on the network can see the data being transferred. There is also no authentication—if you know the filename, you can usually grab it.
Reliability Issues: Because it uses UDP, it can struggle on congested or "lossy" networks (like the open internet).
Block Size Limitations: The original 512-byte block size can make transferring large files (like 1GB OS images) very slow, though modern extensions (RFC 2348) allow for larger blocks. Best Practices for Running a TFTP Server If you are setting one up, keep these three rules in mind:
Isolate the Network: Only run TFTP on a trusted, private management VLAN. Never expose a TFTP server to the public internet.
Read-Only Permissions: Set your server to "Read-Only" unless you are specifically performing a backup or firmware upload. Have a TFTP war story or a clever use case
Modern Enhancements: Use a server that supports "Blocksize Negotiation" to speed up transfers of larger files.
The TFTP server is a testament to the idea that "simple is better." While it isn't the right tool for moving sensitive documents or large media libraries, it remains the gold standard for the low-level tasks that keep our networks running. AI responses may include mistakes. Learn more
Linux installation tools like kickstart (Red Hat) and preseed (Debian) often fetch their configuration files from a TFTP server during stage 1 of installation.
Directory structure for a BIOS PXE server:
/srv/tftp/
├── pxelinux.0
├── ldlinux.c32
├── menu.c32
├── pxelinux.cfg/
│ └── default
├── images/
│ ├── vmlinuz
│ └── initrd.img
pxelinux.cfg/default snippet:
DEFAULT menu.c32
LABEL linux
KERNEL images/vmlinuz
APPEND initrd=images/initrd.img root=/dev/nfs nfsroot=192.168.1.10:/srv/nfsroot
Client (DHCP next-server option points to TFTP server IP):
DHCP option 66 (next-server) = 192.168.1.10
DHCP option 67 (bootfile) = pxelinux.0
Each data block (512 bytes by default, but can use “block size option” extension RFC 2348) must be acknowledged before the next block is sent.
Client TFTP Server
|--- RRQ (file) --------->|
|<-------- DATA (block 1) -|
|--- ACK (block 1) ------->|
|<-------- DATA (block 2) -|
|--- ACK (block 2) ------->|
|<-------- DATA (last, <512)|
|--- ACK (last) ---------->|
If an ACK is lost, the sender retransmits the last data block after a timeout (default 5 seconds).
If you work in IT, specifically in networking or systems administration, a TFTP (Trivial File Transfer Protocol) server is one of those tools you rarely think about until you desperately need it. It isn't flashy, it doesn't have a GUI full of graphs, and it is intentionally simple.
The Verdict: A TFTP server is an essential utility for network engineers. It allows for the transfer of files (like router firmware or switch configurations) without the overhead of authentication or complex setup. While the protocol itself is insecure by modern standards, the software that runs it is vital for infrastructure management.
The standard daemon for Ubuntu/Debian/RHEL.
Quick answers to what people ask the most.