As of 2025, the creators behind this keyword have hinted at a full-length feature film titled "73/420: The Final Cheat." Additionally, merchandise featuring the iconic "Battery Petti" and "Auto Anna" is rumored to be launching soon.
The filmography continues to grow at a rate of roughly 2-3 new videos per week. For fans of Tamil digital content, this is a golden era.
While there isn't a single film titled 73 420, the filmography associated with this trend encompasses a specific genre of Tamil cinema released between 1995 and 2005. This was the golden era of the "Comedy Track"—scenes that often existed independently of the main plot.
Key Films in the "73 420" Canon:
In Tamil film fandom, numbers are not cold—they are ritualistic.
Together, "73 420" becomes a mnemonic key for a specific cinematic flavor: 1970s mass hero meets 1980s comedy-thriller structure. Fans searching this term are not looking for a single film—they want a curated mood: vintage grain, witty dialogue, and the swagger of an anti-hero who cheats only the corrupt.
In the vast and vibrant ecosystem of Tamil cinema and digital content, certain codes and keywords gain cult status. One such intriguing search term that has been circulating among avid fans and casual scrollers alike is "Tamil 73 420 filmography and popular videos." At first glance, this string of numbers and words seems cryptic. However, it represents a unique niche within Tamil entertainment—often linked to a specific channel, a collection of short films, or a thematic series of skits and cinematic clips.
This article serves as the ultimate guide to understanding what "Tamil 73 420" refers to, tracing its filmography, listing the most popular videos, and explaining why this keyword has become a significant touchpoint for digital Tamil content.
Most videos under this banner run between 3 to 7 minutes—perfect for mobile data users in Tamil Nadu. The creators mastered the "hook" within the first 15 seconds, which is why algorithms push "Tamil 73 420" to the top of recommendations.
Tamil 73 420 is not a mainstream cinema star but a digital-first Tamil comedian and satirist whose filmography is rooted in YouTube and short-form video. If you enjoy Tamil comedy skits, meme-driven storytelling, and sharp social commentary, his popular videos are worth a watch. tamil sex videos 73 420 wap com 3gp top
Would you like a list of direct links to the top 5 videos or an update on his 2026 releases?
Review:
If you're looking for Tamil videos, 73 420 wap com top seems to be a platform that offers a collection of Tamil content. Here's a brief overview:
However, I would like to know more about your specific experience with the platform. Have you encountered any issues while using it? Are there any particular features or content that you like or dislike?
If you provide more information or clarify what you're looking for in a review, I'd be happy to help you draft a more detailed and accurate assessment.
: An action-drama starring Snehan and Meghana Raj. The story follows a young man who uses his wit to navigate a world of deception. 420 (Tamil Dubbed)
: A popular dubbed version of a Telugu action film starring Nagendra Babu and Jayamalini, directed by E.V.V. Satyanarayana.
1973 Classics: This was a landmark year for icons like Sivaji Ganesan and Kamal Haasan , featuring major releases like Arangetram and 📹 Popular Videos & Trends
Online, these terms are frequently associated with specific YouTube collections and cultural memes. As of 2025, the creators behind this keyword
Action & Comedy Channels: Channels like Eros Universe Tamil and Super Good Films host high-definition versions of classic and action-heavy Tamil "420-style" movies.
Stoner Comedy Discussions: In online communities like Reddit's r/kuttichevuru
, fans often use "420" to describe "stoner-friendly" or surreal Tamil comedies, frequently citing films like Panchatanthiram or Soodhu Kavvum
Top Video Lists: Recent viral videos often highlight the greatest Tamil films from the last few decades, showcasing the evolution from 70s classics to modern blockbusters.
While there is no single entity or film explicitly titled "Tamil 73 420," the figures 73 and 420 are significant in the context of legendary South Indian actor
, who is currently 73 years old and has acted in over 420 films. Though primarily a stalwart of Malayalam cinema, his extensive Tamil filmography and iconic videos have made him a revered figure in the Tamil industry as well. Mammootty's Tamil Filmography Highlights
Mammootty's contribution to Tamil cinema is marked by performances that redefined the "tough yet emotional" protagonist. His career, spanning five decades, includes some of the most influential films in Tamil cinema history. Thalapathi
(1991): Directed by Mani Ratnam, this remains his most iconic Tamil film. He played Deva, a local underworld leader, alongside Rajinikanth. The film is celebrated for its portrayal of friendship and loyalty. Kandukondain Kandukondain
(2000): A modern adaptation of Jane Austen's Sense and Sensibility, where he portrayed Major Bala, a war veteran. This film showcased his versatility in handling sensitive, romantic drama. Together, "73 420" becomes a mnemonic key for
(1991): Directed by K. Balachander, this film saw Mammootty in a suave, sophisticated role as a father of four navigating a second chance at love. Mounam Sammadham
(1990): His debut in a lead role in Tamil cinema, where he played a brilliant lawyer, setting the stage for his successful crossover from the Malayalam industry.
(2018): A critically acclaimed modern masterpiece where he played a father struggling to raise his daughter with spasticity. His performance was hailed by reviewers as a return to form for the veteran. Popular Videos and Cultural Impact
Mammootty’s popularity in Tamil Nadu is sustained by viral clips and "evergreen" movie moments often shared on social platforms. The "Deva-Surya" Brotherhood: Clips from Thalapathi
, especially the "Chinna Thayaval" song and emotional confrontations with Rajinikanth, remain some of the most-watched Tamil film moments on YouTube and social media.
Style and Agelessness: At 73, Mammootty is frequently the subject of viral videos focused on his "age-defying" looks and fitness, earning him a cult following among younger audiences who view him as a style icon.
Interviews and Wisdom: As a "senior artist," his interviews are highly sought after by film buffs for his deep technical knowledge of filmmaking and the evolution of South Indian cinema. Legacy in the "73 and 420" Context
Mammootty’s "420+ films" milestone represents a vast range of characters, from the rebellious youth to the authoritative patriarch. His ability to maintain a "towering presence" at 73 ensures that his filmography continues to grow, bridge cultural gaps between Tamil and Malayalam audiences, and inspire the next generation of actors.
The term "filmography" here is fluid, as most projects are short films (ranging from 10 to 30 minutes). Unlike theatrical releases, these are primarily hosted on YouTube. Below is a categorized list of their major works.
This period saw the keyword gaining traction, with many videos crossing millions of views.
testssl.sh is free and open source software. You can use it under the terms of GPLv2, please review the License before using it.
Development takes place at github. We're now @ 3.2.3 (stable) and 3.3dev.
There was a last release of 3.0.10 (oldstable) but that was the last one in the 3.0.x branch.
Supported will always be the current dev version and the version before (n-1 rule). As soon as the dev version becomes the stable release, this will be the n-1 version and receives bugfixes only. The dev version has historically not delivered really broken software (no facebook paradigm). Consider it like a rolling release: It'll definitely change-- that is the point of development-- things might break for you if you e.g. expect the output or features all to be the same. But other than that: The dev version itself won't break (TM).
3.2 is the stable branch. There was one final 3.0.10 release, a.k.a the old stable. If you need longer support for 3.0.x there's a possibility for paid maintenance support. We are focussing on 3.3dev, further development will take place in that branch. We aim to not break things badly but, as said, things will change. If you want to make use of new features like QUIC, TLS 1.3 0-RTT, newer SSLlabs rating, check for the Opossum vulnerability and more, you should consider this branch.
-testssl.sh is pretty much portable/compatible. It is working on every Linux, Mac OS X, FreeBSD distribution, on MSYS2/Cygwin (slow).
It is supposed also to work on any other unixoid systems.
A newer OpenSSL version (1.0) is recommended though. /bin/bash is a prerequisite –
otherwise there would be no sockets.
openssl <verify|ocsp|pkey> . In principle any OpenSSL or even LibreSSL can be used as a helper. It's recommended to
use the one supplied as it makes sure special tests or features like IPv6, proxy support, STARTTLS MySQL or PostgreSQL are supported. (The one supplied stems
originally from github.com/PeterMosmans/openssl. openssl-1.0.2k-chacha.pm.ipv6.Linux+FreeBSD.tar.gz is a Linux- and FreeBSD-only tarball. The directory openssl-1.0.2i-chacha.pm.ipv6.contributed/ contains contributed builds for ARM7l and Darwin binaries).
curl -L https://testssl.sh or wget -O - https://testssl.sh pulls the current stable code from here curl -L https://testssl.sh/dev/ or wget -O - https://testssl.sh/dev/ pulls the current development code from githubuserid@somehost:~ % testssl.sh
"testssl.sh [options] <URI>" or "testssl.sh <options>"
"testssl.sh <options>", where <options> is:
--help what you're looking at
-b, --banner displays banner + version of testssl.sh
-v, --version same as previous
-V, --local pretty print all local ciphers
-V, --local <pattern> which local ciphers with <pattern> are available? If pattern is not a number: word match
<pattern> is always an ignore case word pattern of cipher hexcode or any other string in the name, kx or bits
"testssl.sh <URI>", where <URI> is:
<URI> host|host:port|URL|URL:port port 443 is default, URL can only contain HTTPS protocol)
"testssl.sh [options] <URI>", where [options] is:
-t, --starttls <protocol> Does a default run against a STARTTLS enabled <protocol,
protocol is <ftp|smtp|lmtp|pop3|imap|xmpp|telnet|ldap|nntp|postgres|mysql>
--xmpphost <to_domain> For STARTTLS enabled XMPP it supplies the XML stream to-'' domain -- sometimes needed
--mx <domain/host> Tests MX records from high to low priority (STARTTLS, port 25)
--file/-iL <fname> Mass testing option: Reads one testssl.sh command line per line from <fname>.
Can be combined with --serial or --parallel. Implicitly turns on "--warnings batch".
Text format 1: Comments via # allowed, EOF signals end of <fname>
Text format 2: nmap output in greppable format (-oG), 1 port per line allowed
--mode <serial|parallel> Mass testing to be done serial (default) or parallel (--parallel is shortcut for the latter)
--warnings <batch|off> "batch" doesn't continue when a testing error is encountered, off continues and skips warnings
--connect-timeout <seconds> useful to avoid hangers. Max <seconds> to wait for the TCP socket connect to return
--openssl-timeout <seconds> useful to avoid hangers. Max <seconds> to wait before openssl connect will be terminated
single check as <options> ("testssl.sh URI" does everything except -E and -g):
-e, --each-cipher checks each local cipher remotely
-E, --cipher-per-proto checks those per protocol
-s, --std, --standard tests certain lists of cipher suites by strength
-p, --protocols checks TLS/SSL protocols (including SPDY/HTTP2)
-g, --grease tests several server implementation bugs like GREASE and size limitations
-S, --server-defaults displays the server's default picks and certificate info
-P, --server-preference displays the server's picks: protocol+cipher
-x, --single-cipher <pattern> tests matched <pattern> of ciphers
(if <pattern> not a number: word match)
-c, --client-simulation test client simulations, see which client negotiates with cipher and protocol
-h, --header, --headers tests HSTS, HPKP, server/app banner, security headers, cookie, reverse proxy, IPv4 address
-U, --vulnerable tests all (of the following) vulnerabilities (if applicable)
-H, --heartbleed tests for Heartbleed vulnerability
-I, --ccs, --ccs-injection tests for CCS injection vulnerability
-T, --ticketbleed tests for Ticketbleed vulnerability in BigIP loadbalancers
-BB, --robot tests for Return of Bleichenbacher's Oracle Threat (ROBOT) vulnerability
-R, --renegotiation tests for renegotiation vulnerabilities
-C, --compression, --crime tests for CRIME vulnerability (TLS compression issue)
-B, --breach tests for BREACH vulnerability (HTTP compression issue)
-O, --poodle tests for POODLE (SSL) vulnerability
-Z, --tls-fallback checks TLS_FALLBACK_SCSV mitigation
-W, --sweet32 tests 64 bit block ciphers (3DES, RC2 and IDEA): SWEET32 vulnerability
-A, --beast tests for BEAST vulnerability
-L, --lucky13 tests for LUCKY13
-F, --freak tests for FREAK vulnerability
-J, --logjam tests for LOGJAM vulnerability
-D, --drown tests for DROWN vulnerability
-f, --pfs, --fs, --nsa checks (perfect) forward secrecy settings
-4, --rc4, --appelbaum which RC4 ciphers are being offered?
tuning / connect options (most also can be preset via environment variables):
--fast omits some checks: using openssl for all ciphers (-e), show only first preferred cipher.
-9, --full includes tests for implementation bugs and cipher per protocol (could disappear)
--bugs enables the "-bugs" option of s_client, needed e.g. for some buggy F5s
--assume-http if protocol check fails it assumes HTTP protocol and enforces HTTP checks
--ssl-native fallback to checks with OpenSSL where sockets are normally used
--openssl <PATH> use this openssl binary (default: look in $PATH, $RUN_DIR of testssl.sh)
--proxy <host:port|auto> (experimental) proxy connects via <host:port>, auto: values from $env ($http(s)_proxy)
-6 also use IPv6. Works only with supporting OpenSSL version and IPv6 connectivity
--ip <ip> a) tests the supplied <ip> v4 or v6 address instead of resolving host(s) in URI
b) arg "one" means: just test the first DNS returns (useful for multiple IPs)
-n, --nodns <min|none> if "none": do not try any DNS lookups, "min" queries A, AAAA and MX records
--sneaky leave less traces in target logs: user agent, referer
--ids-friendly skips a few vulnerability checks which may cause IDSs to block the scanning IP
--phone-out allow to contact external servers for CRL download and querying OCSP responder
--add-ca <cafile> path to <cafile> or a comma separated list of CA files enables test against additional CAs.
--basicauth <user:pass> provide HTTP basic auth information.
output options (can also be preset via environment variables):
--quiet don't output the banner. By doing this you acknowledge usage terms normally appearing in the banner
--wide wide output for tests like RC4, BEAST. PFS also with hexcode, kx, strength, RFC name
--show-each for wide outputs: display all ciphers tested -- not only succeeded ones
--mapping <openssl| openssl: use the OpenSSL cipher suite name as the primary name cipher suite name form (default)
iana|rfc -> use the IANA/(RFC) cipher suite name as the primary name cipher suite name form
no-openssl| -> don't display the OpenSSL cipher suite name, display IANA/(RFC) names only
no-iana|no-rfc> -> don't display the IANA/(RFC) cipher suite name, display OpenSSL names only
--color <0|1|2|3> 0: no escape or other codes, 1: b/w escape codes, 2: color (default), 3: extra color (color all ciphers)
--colorblind swap green and blue in the output
--debug <0-6> 1: screen output normal but keeps debug output in /tmp/. 2-6: see "grep -A 5 '^DEBUG=' testssl.sh"
file output options (can also be preset via environment variables)
--log, --logging logs stdout to '${NODE}-p${port}${YYYYMMDD-HHMM}.log' in current working directory (cwd)
--logfile|-oL <logfile> logs stdout to 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}.log'. If 'logfile' is a dir or to a specified 'logfile'
--json additional output of findings to flat JSON file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
--jsonfile|-oj <jsonfile> additional output to the specified flat JSON file or directory, similar to --logfile
--json-pretty additional JSON structured output of findings to a file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
--jsonfile-pretty|-oJ <jsonfile> additional JSON structured output to the specified file or directory, similar to --logfile
--csv additional output of findings to CSV file '${NODE}-p${port}${YYYYMMDD-HHMM}.csv' in cwd or directory
--csvfile|-oC <csvfile> additional output as CSV to the specified file or directory, similar to --logfile
--html additional output as HTML to file '${NODE}-p${port}${YYYYMMDD-HHMM}.html'
--htmlfile|-oH <htmlfile> additional output as HTML to the specified file or directory, similar to --logfile
--out(f,F)ile|-oa/-oA <fname> log to a LOG,JSON,CSV,HTML file (see nmap). -oA/-oa: pretty/flat JSON.
"auto" uses '${NODE}-p${port}${YYYYMMDD-HHMM}'. If fname if a dir uses 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}'
--hints additional hints to findings
--severity <severity> severities with lower level will be filtered for CSV+JSON, possible values <LOW|MEDIUM|HIGH|CRITICAL>
--append if (non-empty) <logfile>, <csvfile>, <jsonfile> or <htmlfile> exists, append to file. Omits any header
--outprefix <fname_prefix> before '${NODE}.' above prepend <fname_prefix>
Options requiring a value can also be called with '=' e.g. testssl.sh -t=smtp --wide --openssl=/usr/bin/openssl <URI>.
<URI> always needs to be the last parameter.
userid@somehost:~ %
testssl.sh --starttls smtp <smtphost>.<tld>:587 testssl.sh --starttls ftp <ftphost>.<tld>:21 testssl.sh -t xmpp <jabberhost>.<tld>:5222 testssl.sh -t xmpp --xmpphost <XMPP domain> <jabberhost>.<tld>:5222 testssl.sh --starttls imap <imaphost>.<tld>:143The ports in those examples above are just the standard ports. Also here you're free to check any port. //refactor those, see e.g. https://content-security-policy.com/unsafe-hashes/ or just drop tis shit
3.2
3.0