A web platform that analyzes raw email headers and text using AI to detect phishing, trace sender transmission paths with geolocation, and generate forensic reports for security analysts.
All India Council for Technical Education (AICTE) · Cyber Security Cell · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Fraudulent Email Detection Engine
An NLP and ML module that scans email text and links to classify phishing, spoofing, and business email compromise risks.
Email Header Analyzer
A module that parses headers like SPF, DKIM, DMARC, and Return-Path to spot anomalies and forged sender fields.
Origin Traceability Module
A component that extracts originating IP addresses from relay chains and maps their geolocation and hosting infrastructure.
Identity Correlation Module
A graph-based tool that links email indicators to known threat data and groups related fraud campaigns.
Analyst Dashboard and Reporting
A dashboard providing real-time alerts, visual trace maps, and structured forensic reports for investigations.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check if the platform can successfully parse raw email headers, accurately trace relay paths back to an IP address, map geolocation, and generate coherent forensic reports.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Specific legal and evidentiary standard requirements for chain of custody?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Integration formats required for existing institutional email servers?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for fraudulent email detection engine. How would you build that?
Decoded from SIH26106 itself — An NLP and ML module that scans email text and links to classify phishing, spoofing, and business email compromise risks. The brief asks for it by name.
Each one is quoted from a gap in the brief, not a guess about your team.
No measurable target
The description asks for early and accurate detection and confidence-based assessments, but never defines a numerical accuracy target or processing speed limit.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for email header analyzer. How would you build that?
Decoded from SIH26106 itself — A module that parses headers like SPF, DKIM, DMARC, and Return-Path to spot anomalies and forged sender fields. The brief asks for it by name.
The brief asks for origin traceability module. How would you build that?
Decoded from SIH26106 itself — A component that extracts originating IP addresses from relay chains and maps their geolocation and hosting infrastructure. The brief asks for it by name.
The brief asks for identity correlation module. How would you build that?
Decoded from SIH26106 itself — A graph-based tool that links email indicators to known threat data and groups related fraud campaigns. The brief asks for it by name.
The brief asks for analyst dashboard and reporting. How would you build that?
Decoded from SIH26106 itself — A dashboard providing real-time alerts, visual trace maps, and structured forensic reports for investigations. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will check if the platform can successfully parse raw email headers, accurately trace relay paths back to an IP address, map geolocation, and generate coherent forensic reports.
This is the evaluator read for your problem statement, decoded from the brief's own wording.