---
title: "Mukaddaskhon Umarova (@hanachan) | Hashnode"
description: "Mukaddaskhon Umarova (@hanachan) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@hanachan"
---

@hanachan

# Mukaddaskhon Umarova

@hanachan · Incheon, South Korea · Joined October 2026

## Comments

[Really clear and beginner-friendly explanation! I especially liked the comparison table and the practical examples of when to use A records versus CNAME records. The section about common mistakes is also very useful because these small DNS configuration errors can cause frustrating issues when setting up a website. One thing I found interesting is how CNAME records allow hosting providers to manage changing IP addresses without requiring users to update their DNS configuration manually. Thanks for breaking down the topic in such an understandable way!](https://hashnode.com/posts/cname-vs-a-record-what-s-the-difference-and-which-one-should-you-use/6adf2ca8f218f0c2c96f7f5e/comment/6ae9abf52122909e2eaeb03f)

Comment · Article · Nov 3 · 1 · [CNAME vs A Record: What's the Difference (and Which One Should You Use?)](https://hashnode.com/posts/cname-vs-a-record-what-s-the-difference-and-which-one-should-you-use/6adf2ca8f218f0c2c96f7f5e)

[Hello! Thank you for the thoughtful suggestions. I really like the idea of using collection. deque to introduce a rolling time window. It would make the detection logic more practical by focusing on repeated failures within a specific period rather than simply counting all failures. I'll work on implementing the four test scenarios (4, 5, and 6 attempts within the window, plus 6 attempts spread across separate windows) and document the results in the next version of the lab. Also, thanks for pointing out the RFC 5737 documentation IP range. I'll keep the synthetic IPs for the current tests and consider using a separate set of public IPs if I introduce geolocation or reputation checks in a future lab. Appreciate it buddy~](https://hashnode.com/posts/threat-atlas-lab-01-building-a-failed-login-detection-tool-with-python/6ae30dfa77708dd380e8762e/comment/6ae87a63b2110c31f41e94ef#reply-6ae9aaff37f25e34e1bd015f)

Reply · Article · Nov 3 · 1 · [Threat Atlas Lab 01: Building a Failed Login Detection Tool with Python](https://hashnode.com/posts/threat-atlas-lab-01-building-a-failed-login-detection-tool-with-python/6ae30dfa77708dd380e8762e)