Frequently Asked Questions

Spexo is an online toolkit for checking internet performance and diagnosing common network or website issues. Choose the relevant tool, enter the requested host, domain or address when needed, and review the result with the guidance shown on that tool page.

Spexo provides its online tools for visitors to use without purchasing a subscription. Some pages may display advertising to support the service. Check the relevant page and current site terms for any usage conditions.

You can run the standard internet speed test directly in your browser without creating an account. If a particular feature asks you to sign in, follow the instructions shown for that feature.

No app or browser extension is required for the browser-based speed test. Open Spexo in a modern browser and start the test from the homepage.

You can use Spexo from a desktop, laptop, tablet or smartphone with a modern browser and an internet connection. Available features can vary with the device and browser capabilities.

Start with the symptom. Use a speed test for connection performance, ping or traceroute for reachability and route issues, DNS tools for name-resolution questions, and domain or website checks for public website configuration.

Each tool is intended to make a specific check easier to interpret. Review the result labels and explanatory text on the tool page; technical results may still require network or hosting knowledge to act on.

Run a speed test more than once, note download, upload and latency, and compare results at different times. If possible, repeat over Ethernet to separate Wi-Fi limitations from the broadband connection.

A browser-based speed test transfers data between your device and a measurement endpoint. It estimates download and upload throughput and measures response time under the conditions present during that test.

Download speed describes how quickly data reaches your device; upload speed describes how quickly your device sends data out. Both are commonly shown in megabits per second (Mbps).

There is no single ideal speed for every household. The amount you need depends on the number of people and devices online, video quality, gaming, video calls, downloads and other simultaneous activity.

Results can change with network congestion, Wi-Fi signal quality, background downloads, device load, routing and the measurement server. Small variations are normal; compare several tests rather than relying on one reading.

Your plan's advertised rate is not always the throughput available to one device at every moment. Wi-Fi, router limits, network congestion, server distance, device performance and other traffic can reduce measured results.

Yes. The route and distance between your device and the test endpoint can affect latency and throughput. A nearby endpoint often reduces route distance, but server load and network peering also matter.

Use Ethernet when you want to assess the broadband connection while minimizing wireless interference. Use Wi-Fi when you want to understand the performance you actually receive around your home or office.

Run several tests under similar conditions and repeat at different times if you suspect congestion. Keep the device, connection type and test setup consistent so the results are easier to compare.

Ping, commonly used to describe latency, is the time taken for a packet to travel to a destination and for a response to return. It is usually measured in milliseconds (ms); lower latency generally means a more responsive connection.

Jitter is variation in packet delay. Large or inconsistent delay changes can make real-time applications such as voice calls, video meetings and online games feel unstable, even when average latency seems acceptable.

Packet loss occurs when packets sent across a network fail to reach their destination. Loss can cause retransmissions, pauses, distorted calls or lag, depending on the application and how much data is lost.

Lower and stable latency is generally better for gaming, but what feels acceptable depends on the game, server location and player expectations. Compare results to the game server you actually use rather than treating one universal threshold as definitive.

Throughput and latency measure different things. A connection can transfer large files quickly but still have a long route, queueing delays, wireless interference or congestion that increases response time.

Yes. Weak signal, interference, crowded channels, distance and competing devices can make wireless delivery inconsistent. Testing near the router or using Ethernet can help identify whether Wi-Fi is contributing.

A timeout means the expected response did not arrive within the test's waiting period. The host may be offline, filtering ICMP, rate-limiting probes or experiencing a network path issue; a timeout alone does not prove a server is down.

Try Ethernet, move closer to the access point, reduce competing traffic, restart network equipment if appropriate and compare another destination. Persistent problems may require your ISP or network administrator to investigate the route.

The Domain Name System (DNS) translates human-readable domain names into records such as IP addresses. If DNS records or resolvers are unavailable or incorrect, a website may fail to load even when the network itself is connected.

An A record maps a hostname to an IPv4 address. An AAAA record maps a hostname to an IPv6 address. A domain can publish either or both, depending on its hosting and network configuration.

MX records identify mail exchangers; TXT records publish text data often used for domain verification and email authentication; CNAME records alias one hostname to another; NS records identify authoritative name servers for a DNS zone.

Resolvers cache DNS answers for the record's time to live (TTL), and different resolvers may refresh at different times. Delegation, authoritative server configuration and cached negative answers can also affect when a change appears.

A public IP address is used for routing across the public internet. Private IPv4 addresses are reserved for internal networks and are not directly globally routable; routers commonly use network address translation to connect private devices to the internet.

IPv4 uses 32-bit addresses, while IPv6 uses 128-bit addresses and provides a much larger address space. They are distinct protocols and a network may support IPv4, IPv6 or dual-stack operation.

Many internet providers assign addresses dynamically or use shared address infrastructure. Your public address may change after reconnecting, lease renewal, network changes or when using a VPN or proxy.

No. DNS lookup shows DNS records and resolution information; it does not validate the full security of a website. Use an SSL/TLS certificate check and other security checks as separate signals.

A domain lookup can show publicly available registration information such as registrar, registration dates, nameservers and domain status. The exact fields depend on the registry, registrar and privacy rules for that extension.

Use a domain expiry or registration lookup to inspect the expiry information published by the relevant registry or registrar. Some extensions do not expose a reliable public expiry date, so confirm important renewals with your registrar.

An SSL/TLS checker can inspect certificate details such as validity dates, issuer, hostname coverage and certificate chain as observed by the checking service. A successful certificate check does not guarantee that an entire website is secure.

An HTTP status code is the server's response category for a request. For example, 2xx indicates success, 3xx redirection, 4xx a client-side/request issue and 5xx a server-side error; the exact code provides more detail.

Redirects may be configured to enforce HTTPS, choose a canonical hostname, move content or route visitors to a new page. Unexpected loops or chains can indicate conflicting rules in the application, server or CDN.

A blacklist checker queries selected reputation or DNS-based block lists to see whether an IP address or domain is listed. A listing is one signal to investigate; lists differ in coverage, criteria and removal processes.

Identify which list reports the entry, review its published reason and remediation process, and investigate the underlying issue before requesting delisting. For email-related listings, check sending practices and SPF, DKIM and DMARC configuration.

No single lookup can guarantee website security. Combine certificate, DNS, HTTP header and reputation checks with secure software updates, access controls, monitoring and a properly scoped security assessment.

Possible causes include DNS resolution failure, captive portal sign-in, browser or proxy settings, firewall rules, router issues or an outage. Test another site and device, then compare DNS resolution and basic connectivity.

Check from another network or device and use an external availability checker. If it fails only on your connection, investigate local DNS, routing, firewall or ISP issues; if it fails from multiple independent networks, the site or hosting may be affected.

Some routers do not respond to traceroute probes or filter the relevant messages. A trace that stops early does not always mean traffic cannot reach the destination; compare with application-level connectivity and other routes.

The configured resolver may be unavailable, a record may be missing or incorrect, DNS cache may be stale, or a VPN/proxy/security product may alter DNS handling. Try another trusted resolver only if your network policy permits it.

Peak-hour congestion can affect Wi-Fi, shared access networks, ISP links or remote services. Compare wired and wireless tests at different times and note whether latency, packet loss or throughput changes most.

Yes. Devices may share limited Wi-Fi airtime and internet bandwidth, especially when streaming, backing up or downloading. Pause heavy activity and retest to see whether contention is contributing.

Record several test results with timestamps, note whether you used Wi-Fi or Ethernet, check more than one destination and capture any error messages. This helps distinguish local wireless problems from wider connectivity issues.

Restarting can clear some temporary router or modem faults, but it will not fix incorrect DNS records, damaged cables, provider outages or persistent configuration problems. Save relevant settings and follow your equipment provider's instructions.

A saved report may include measured download and upload speeds, latency, jitter, packet loss, test time and endpoint details where those fields were captured. The exact report depends on the data available for that test.

Use the report or print controls provided with the completed result or test-history interface. Browser print dialogs commonly allow you to print a report or choose Save as PDF.

A report records an earlier measurement, while a new test measures current conditions. Network load, route, Wi-Fi quality, device activity and endpoint conditions may have changed between runs.

Compare tests taken with similar devices, connection types, server locations and network activity. Look at latency and stability as well as download/upload throughput, and consider the time of day.

A single test does not identify every cause of poor performance, guarantee the speed available to every device, or prove that a website or network is secure. It is one measurement from a particular device and route at a particular time.

Some fields depend on browser permissions, device capabilities, endpoint responses or what the application recorded. A missing value should not be interpreted as zero unless the report explicitly says so.

Repeated, timestamped results can help explain a problem, especially when you record the connection type and test conditions. Your provider may still run its own diagnostics and use its own measurement criteria.

Use the Clear History control if it is available in the homepage history section. Review the confirmation before clearing; locally saved history and server-side records, if any, may be governed by different controls and policies.

Some network diagnostics rely on the IP address visible to the service or on an IP address you enter. The data needed depends on the tool. Review the Privacy Policy for details about information handled by the site.

Refer to the current Spexo Privacy Policy for the site's data practices. The policy is the authoritative place to review whether personal information is sold, shared or processed and for what purposes.

Do not assume that a result is public or private based only on the interface. Review the Privacy Policy and the controls shown with the test history or report feature to understand how a particular record is stored and displayed.

Looking up publicly available DNS, registration or reachability information is different from attempting access or scanning. Only test systems you own or are explicitly authorized to assess, and follow applicable laws and service terms.

The tools can provide useful initial measurements and public configuration checks. For production decisions, combine results with your own monitoring, documented authorization and qualified network or security review.

Do not submit passwords, private keys, authentication tokens, confidential URLs or other secrets. Enter only the public hostname, IP address or information required for the specific diagnostic.

Use the policy links in the site footer to review the Privacy Policy, Terms of Service, Disclaimer, Cookie Policy and other published policies.

Use the Contact page and describe the tool, the time of the issue, your browser and device, connection type and any non-sensitive error message. Do not include passwords or private credentials.