Study of 288 Cloud IPs Finds 4.5% Blocklisted and Uneven Reverse DNS Coverage

·52 views

A developer sampled 288 IP addresses from AWS, GCP, and Cloudflare's publicly published ranges to assess their reputation across four metrics: reverse DNS, mail blocklists, BGP announcements, and RDAP records. All 123 GCP IPs had valid PTR records, roughly half of AWS IPs did, while only one of 15 Cloudflare IPs carried a reverse DNS entry, reflecting those ranges' proxy-focused purpose. Thirteen of the 288 IPs — about 4.5% — appeared on at least one public mail blocklist, with Cloudflare's small sample showing the highest rate at 33%. BGP data revealed that some IPs within AWS-published ranges are actually announced by third-party networks, including Verizon Business and YouTube's Irish AS, due to customers bringing their own IP space. The author notes the true blocklist rate is likely higher since Spamhaus, one of the most authoritative sources, could not be queried in this setup.

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)

Auditing Terraform for Cloud Lock-In Before Migrating to a European Provider

Engineers planning a move off a hyperscaler can scan their Terraform files and state to find lock-in before migrating. Resources should be sorted into three tiers: standard portable components such as VMs, PostgreSQL, and S3-compatible storage; managed services needing config changes; and proprietary services like DynamoDB or BigQuery that force application code rewrites. The audit should also cover application dependencies, since a resource only creates real lock-in when code calls its proprietary SDK directly rather than a standard protocol. The article notes that Terraform standardizes provisioning syntax but does not make infrastructure portable, because each provider uses distinct resource names and APIs. Teams are advised to run scanners in CI/CD pull requests to prevent new proprietary dependencies while planning the migration.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Seven Proxy Providers Compared for Web Scraping and Automation Developers

A DEV Community post from Dev Stack Hub reviews seven leading proxy providers for developers working on web scraping and automation. The article compares the providers' features to help readers identify which option suits their development needs. It is positioned as a discussion piece tagged around web scraping and Python. The post was published on November 8 and runs about 12 minutes to read. The available text does not detail the specific providers or their individual findings.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

n8n Tops Nine-Tool Comparison of AI Workflow Automation Platforms for 2027

A new comparison evaluates nine AI workflow automation tools, which link business apps and insert AI models into the steps between them. The assessment scores each tool on eight criteria, split between reliability (output validation, failure handling, run visibility) and governance (identity, policy, audit trail, change control, hosting and data controls). n8n ranks first overall, with the highest reliability score at 89%, and suits teams that want to self-host and choose their own model. Barndoor Automations and UiPath tie for second place with identical overall scores of 66.7, while the remaining six tools fall within 3.3 points of one another. The author cautions against reading closely into the order of the lower-ranked tools given how narrow the gaps are.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Seven Pitfalls That Distort Latency Arbitrage Measurements, and How to Check for Them

Measuring how long a broker's quote lags behind a faster price feed appears simple but is easily skewed by the measurement method itself. The author, testing XAUUSD quotes at three retail brokers, compiled a checklist of common traps that make stale-quote windows seem more frequent, longer, or more profitable than they are. Key issues include clock drift between separately timestamped feeds, one-second snapshots that erase sub-second windows, and comparing mid prices instead of the tradable cross-side spread. A second fast feed showed more windows per hour but also many crossed or zero-spread quotes, so its extra windows were mostly noise. Each pitfall is paired with a concrete check the reader can run on their own data.

0 comments Read more at DEV Community