Linux Roller

Salieron parches para PHP2Shell: dos fallas críticas (CVSS 4.0: 9.2) que pueden permitir ejecutar código sin autenticación. Aviso y versiones: php.net/archive/2026.php#202… Un servidor puede funcionar perfectamente y aun así ser vulnerable. Actualizar tiene que ser rutina.

En Emprender 2026, UNLaM 🚀 #lamatanzaemprende #ponetela10

The WordPress REST API is not something you should automatically disable. Modern WordPress depends on it. How do I secure the WordPress REST API without breaking WordPress? axrglobal.com/wordpress-rest…

Should you block /wp-json/ to make WordPress more secure? Probably not. The REST API powers parts of WordPress you probably don't want to break.

If your site is down, don't touch DNS blindly. Follow the chain. More on this → axrglobal.com How many times did you "fix" DNS when the real issue was something else? 👇

DNS can resolve perfectly while the real problem is something else: — server is down — SSL misconfigured — hosting account suspended — app throwing errors DNS is the messenger, not the message.

Why do two people see different things on the same domain? Caching. Resolvers hold onto the answer based on TTL. Nobody's "wrong" — they just haven't seen the change yet. Golden rule: make one change, document it, wait, then test.

Step 3: match the symptom to the record. ❌ Email broken, website works → check MX, SPF, DKIM, DMARC ❌ "www" broken, root domain works → check the CNAME/A for www ❌ Old site still showing → that's caching, not the record

Step 2: check the nameservers. Classic migration mistake: you moved the site to a new host, but the domain is still pointing at the old host's nameservers. Result: your new A record doesn't exist for anyone.

Step 1: check the domain. Is it active? Is auto-renewal set up? Do you have access to the registrar account? Without this, you can't touch anything else. It's the foundation.