SShortSingh.
Back to feed

WHOIS Protocol Failing Silently on Up to 60% of Lookups as RDAP Takes Over

0
·1 views

The decades-old WHOIS protocol, which relies on unstructured plain-text responses over TCP port 43, has been deteriorating for years and is now failing on an estimated 30–60% of domain lookups. ICANN's RDAP compliance mandate, enforced from August 2024, effectively broke legacy WHOIS endpoints for gTLD registrars still using them. Simultaneously, major data providers like WhoisXML API eliminated free tiers and raised pricing minimums, pushing teams toward paid alternatives. RDAP, standardized via RFC 7480–7484, offers a structured JSON-based replacement that addresses WHOIS's lack of schema, encoding standards, and error signaling. In response, developers have built RDAP-first tools — such as the Apify actor described here — that fall back to legacy WHOIS only for unmigrated TLDs and return a unified JSON schema across all domains.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Claude Projects and Skills Can Eliminate Repetitive Prompt Setup for Good

A DEV Community guide outlines how users can stop rewriting the same instructions in every Claude session by using two built-in features: Projects and Skills. Claude Projects act as persistent containers where users store system prompts and knowledge files — such as brand guidelines, audience personas, and style guides — that automatically apply to every conversation within that project. Skills extend this further by saving entire workflows as reusable commands triggerable with a single sentence. Setting up a Project involves naming it clearly, writing a detailed system prompt covering role, context, and output standards, and uploading relevant reference documents. Together, these features transform Claude from a blank-slate tool into a pre-configured system that retains context across unlimited conversations without repeated setup.

0
ProgrammingDEV Community ·

Anthropic's Amodei Calls for AI Regulation While Critics Warn of Regulatory Capture

Anthropic CEO Dario Amodei published a lengthy essay titled 'Policy on the AI Exponential,' arguing that AI will soon deliver humanity 'almost unimaginable power' and that governments must be able to test, gate, and block frontier models before deployment. His proposed framework includes mandatory third-party testing, authorized evaluators, security standards, and government authority to halt deployments that fail safety checks. Critics, including Turing Award winner Yann LeCun, argue the proposal amounts to regulatory capture, warning that compute-based thresholds would burden smaller developers and open-source projects far more than well-resourced labs like Anthropic. The debate coincides with a separate industry development: Coinbase reportedly cut its AI spending by nearly half through open models, smarter routing, and better caching. Together, the two events highlight a growing tension between the consolidating power of frontier AI labs and the expanding accessibility of lower-cost, open alternatives.

0
ProgrammingDEV Community ·

Why catching npm vulnerabilities in CI is already too late

Software engineer Sonu Kapoor, writing for DevOps.com, argues that discovering npm dependency vulnerabilities during CI pipeline runs is a structural flaw, not a security practice. By the time a scanner flags an issue in CI, the developer has already installed the package, written dependent code, and moved on, making the fix a separate project rather than a quick decision. To illustrate the scale of the problem, Kapoor cites a scan of the NestJS repository's package-lock.json, which revealed 1,626 resolved packages carrying 25 vulnerabilities, 13 of which were buried in transitive dependencies. The recommended fix involves shifting discovery earlier through pre-commit hooks, mandatory PR-level lockfile scans, and branch-protection policies, rather than relying solely on a local CLI tool. Critics of the approach note that developer-side tools can be inconsistently applied, and that enforced PR checks and branch-protection rules offer more reliable controls than optional local scanning.

0
ProgrammingDEV Community ·

TinyML on ESP32 Enables Real-Time Heart Arrhythmia Detection Without Cloud

Developers are deploying TinyML models directly on ESP32 microcontrollers to detect cardiac arrhythmias in real time from raw ECG signals, eliminating the need for cloud processing. The system uses TensorFlow Lite for Microcontrollers paired with an AD8232 ECG sensor to capture, filter, and analyze heart rhythm data entirely on-device. A 1D Convolutional Neural Network trained on the MIT-BIH Arrhythmia Database is converted to an 8-bit integer format via post-training quantization, reducing model size fourfold and speeding up inference. This edge-based approach addresses key concerns around latency, battery consumption, and patient data privacy by keeping sensitive medical information local. Abnormal rhythm detections can trigger alerts sent to a mobile dashboard via Bluetooth or Wi-Fi.

WHOIS Protocol Failing Silently on Up to 60% of Lookups as RDAP Takes Over · ShortSingh