10.46243/jst.2023.v8.i06.pp158-162 registered
Effective And Efficient Detection Of Phishing Emails Using Machine Learning
Resolves to https://www.jst.org.in/index.php/pub/article/view/757
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2023.v8.i06.pp158-162
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 02c257279d96f266…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Effective And Efficient Detection Of Phishing Emails Using Machine Learning (PrincipalTitle · en)
Published 2023-08-07
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 8 · issue 7 · pages 158–162
Agents
- Moola.Akshitha Moola.Akshitha (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2023.v8.i06.pp158-162
Abstract · en
Emails are widely used for personal and professional communication,often involving the transmission of sensitive information like banking details,credit reports,and login data.Consequently,these emails become valuable targets for cyber criminals who seek to exploit such knowledge for their own malicious purposes.Phishing, a deceptive technique employed by these individuals,involves impersonating well-known sources to deceive and extract sensitive information from unsuspecting individuals.The sender of a phishing email uses false pretenses to persuade recipients into disclosed personal information.In this work,the detection of phishing emails is learning methods to categorize emails as either genuine or phishing attempts.LMT classifiers have proven highly effective in accurately classifying emails,achieving optimal accuracy in email classification tasks.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2023.v8.i06.pp158-162 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Effective And Efficient Detection Of Phishing Emails Using Machine Learning (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Moola.Akshitha Moola.Akshitha publisher: Longman Publishers published: 2023-08-07 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 8 · no. 7 · pp. 158–162 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
References with DOIs
The record lists 10 references; 8 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 1 | ref1 Aleroud,A.,&zhou,L.(2017).Phishing e n v i r o n m e n t s, t e c h n i q u e s, a n d countermeasures:A survey.Computers &security,68,160-196 | 10.1016/j.cose.2017.04.006 | not held here |
| 2 | ref2 Vayansky,I.,&Kumar,S.(2018).Phishingchallenges and solutions.Computer Fraud & Security,2018,15-20 | 10.1016/s1361-3723(18)30007-1 | not held here |
| 3 | ref3 E. J. Williams and colleagues, “Exploring susceptibility to phishing in the workplace,” International Journal of Human-Computer Studies, vol. 120, no. 1, 2018, pp. 1–13 | 10.1016/j.ijhcs.2018.06.004 | not held here |
| 4 | ref4 A. Odeh et al., “Machine Learning Techniques for Detection of Website Phishing: A Review for Promises and Challenges,” IEEE, 2021, 11th Annual Computing and Communication Workshop… | 10.1109/ccwc51732.2021.9375997 | not held here |
| 6 | ref6 “PHIBOOST-a novel phishing detection model using Adaptive boosting approach,” Jordanian Journal of Computers and Information Technology (JJCIT), vol. 7, 2021 | 10.5455/jjcit.71-1600061738 | not held here |
| 7 | ref7 K. L.Chiew et al. (2018) “A survey of phishing attacks: Their types, vectors, and technical approaches,” Expert Systems with Applications, vol. 106, pp. 1–20 | 10.1016/j.eswa.2018.03.050 | not held here |
| 8 | ref8 M. Al-Fayoumi et al., “Intelligent association classification technique for phishing website detection,” International Arab Journal of Information Technology, vol. 17, 2020, pp. 4… | 10.34028/iajit/17/4/7 | not held here |
| 9 | ref9 Why do consumers not report spear phishing emails? [9] Y. Kwak et al., Telematics and Informatics, vol. 48, p. 101343, 2020 | 10.1016/j.tele.2020.101343 | not held here |
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 80 fields set · sha256 46587361065b… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | agents.0.name.family: agents.0.name.given: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 07 Oct 2026, 07:37 | Metadata completed abstract (118 words) · licence | ● accepted by Crossref | 1ed06f223e03… |
| 07 Oct 2026, 08:23 | Read back: Crossref's record shows it | ● confirmed | 3e93ddd9d702… |
2 entries · the last fingerprint 3e93ddd9d70218d172a7622db9b54f21703f8022f4eabe9f5ce06af3924b3f69 · the history as JSON, each entry with the fingerprint before it, to check them yourself.



