Is it down for everyone or just you?
Enter any website address below to check if it's currently down for everyone worldwide, or if an outage is isolated to your computer.
Deep Diagnostics Suite Running...
Performing live server trace. We are contacting domain, resolving regional DNS records, measuring HTTP load latency, and preparing advanced AI-powered health diagnosis.
DNS lookup
Port handshake
HTTP headers
AI processing
AVAILABILITY REPORT
phpinfo.dev
🔴 CONFIRMED OFFLINE. The site is currently inaccessible from our server probe node.
Response Latency
7003ms
Tested Realtime
IP
Resolved IP
31.214.178.54
HTTP
Response Code
None / Timeout
PING
Status Check
DOWN (OFFLINE)
SRV
Server Type
Proxy Header Hidden
Live Report
Why phpinfo.dev is down
The host for Phpinfo did not reply to our network queries, resulting in a connection timeout.
Deeper Technical Breakdowns:
Our check was cancelled after failing to complete a standard TCP port handshake with the host at 31.214.178.54 within our 7000ms threshold. Utilizing an active regional top-level extension (.dev), this domain targets specific geographic localization routing rules, local caching nodes, and region-bound server filters. For a high-load developer and cloud service hub, total silence indicates either the server is completely shut down or active routing barriers are discarding incoming packets. A warning-level delay of 7003ms was verified. This severe latency indicates massive server resource constraints (CPU/RAM throttling), an overloaded database query pool, or multi-hop routing bottlenecks delaying the payload generation.
Potential Server Outage Causes:
#1
The virtual server or hardware host is completely powered down, dead, or locked due to infrastructure issues
#2
The network interface is encountering a massive Distributed Denial of Service (DDoS) packet flood
#3
Active server firewalls (Fail2ban, iptables, Security Groups) are silently discarding our trace scanning packets
#4
Localized routing loop anomalies on core transit routers, preventing packets from completing handshakes
Share Diagnostic Status
Share this real-time availability status for phpinfo.dev. Let colleagues or visitors know if the site is globally reachable or experiencing downtime.
💡
Help, FAQs & Diagnostic Hub
Comprehensive support guidelines and technical network documentation
If a webpage is 'Down for everyone', it indicates the website's servers are experiencing global issues, misconfigured DNS settings, hardware failures, or network provider outages. If it is 'Down for just you', our remote node successfully connected, signifying the connection layout is active but blocked somewhere on your local machine, home router, local Internet Service Provider (ISP), or by active regional censorship firewalls.
These are standardized HTTP status codes representing server-side failures:
• 500 Internal Server Error: This represents a generic unhandled exception, syntax issue, or unexpected crash in the backend code (PHP, Node, Python, etc.) or database desynchronization.
• 502 Bad Gateway: The upstream server or reverse proxy receives an invalid query response or no response from the underlying application processes.
• 503 Service Unavailable: The application is temporarily overloaded beyond processing queues, undergoing critical database migrations, or is offline for scheduled maintenance.
• 504 Gateway Timeout: The primary application thread was slow compiling calculations and exceeded the safety timeout limits of the fronting proxy.
The Domain Name System (DNS) operates as the internet's telephone infrastructure, mapping easy-to-read domains (like example.com) into physical machine network sockets (IP addresses). A DNS failure occurs when authoritative nameservers refuse, fail, or do not respond to record lookups. This usually happens when the domain registration has expired, nameserver delegation entries are misconfigured at the registrar level, or DNSSEC cryptographic validation fails, forcing browsers to drop the mapping requests to protect client security.
Computers and mobile carriers route traffic over fundamentally separate backbones. Your mobile cellular network (LTE/5G) utilizes carrier DNS towers which frequently update and bypass home Wi-Fi gateway caches. Meanwhile, your computer's operating system and desktop browser cache old DNS address tables historically to speed up loading. If a website recently migrated to a new host, your mobile network might receive the new address immediately, while your home router or operating system struggles with cached desynchronization for up to 48 hours.
Each time you run a query, our host server triggers an instantaneous, isolated network trace directly from our dedicated testing nodes. We execute a live DNS lookup, establish a TCP socket link on active ports, and parse the full HTTP header response via a custom cURL stream. We do not report stale browser caches or mock historical records, guaranteeing 100% active operational accuracy.
An SSL/TLS error signifies that the secure encryption key presented by the website is invalid, expired, or untrusted. This can be caused by (1) failure of automatic certificate renewals (like Let's Encrypt cron errors), (2) a domain mismatch where the key covers subdomains but not the root URL, or (3) utilizing an insecure self-signed key. Bypassing these errors is highly discouraged as it disables modern end-to-end encryption, exposing your private passwords, session cookies, and sensitive financial data to packet sniffing or man-in-the-middle attacks.
ISP throttling and content filtering occur when a local Internet Service Provider actively slows down or filters specific traffic streams due to parental control layers, corporate network policies, or state-level firewalls. DNS Hijacking is a related mechanism where the ISP intercepts your standard DNS requests and redirects you to a placeholder billing/warning page instead of the actual destination. You can easily diagnose this by comparing results on our global nodes, or bypass it by using a premium VPN or configuring encrypted DNS protocols like DNS-over-HTTPS (DoH) inside modern browsers.
This phenomenon denotes a partial connection failure where the main HTML page templates load successfully, but the accompanying styling (CSS), interactive scripts (JS), or assets (images) fail to load. Major causes are (1) browser privacy extensions or over-aggressive ad-blockers blacklisting CDN endpoints, (2) Mixed Content security overrides where the site is served over HTTPS but attempts to fetch stylesheets over insecure HTTP, or (3) CDN origin desynchronization during ongoing site migrations.
These client-side browser errors are triggered when the connection is established but then severed mid-handshake. "Connection Reset" means the target host or an intermediate network router actively forced a socket termination, typically due to custom local antivirus filters, corporate proxy rules, or MTU packet size desynchronization. "Empty Response" indicates the server processed the request but returned absolutely zero bytes of data, pointing to an immediate code process crash or a misconfigured upstream port forwarding gateway.
Checking Node Online
Always trust the Checker!
If our checker reports a site is ONLINE, the bottleneck resides inside your local hardware or local networks 100% of the time.
Clear cookies or flush OS DNS resolvers
immediately!
Your Network Node Latency Check
Measure the direct response time of your browser right now.
Connecting...
No connection checked. Trigger local analysis below.
CLIENT LATENCY OK
Recent status checks
phpinfo.dev
UTC Timestamp: 2026-06-21 02:21:22
Just now
DOWN
fujitsuweb.au
UTC Timestamp: 2026-06-21 02:21:09
Just now
DOWN
index.php.sample
UTC Timestamp: 2026-06-21 02:21:07
Just now
DOWN
shopifystore.net
UTC Timestamp: 2026-06-21 02:21:05
Just now
DOWN
application.yml.sample
UTC Timestamp: 2026-06-21 02:20:42
Just now
DOWN
ford.net
UTC Timestamp: 2026-06-21 02:20:21
1 minute ago
DOWN
nintendocloud.biz
UTC Timestamp: 2026-06-21 02:20:16
1 minute ago
DOWN
index.php.master
UTC Timestamp: 2026-06-21 02:19:04
2 minutes ago
DOWN