Result Summary
c-98-248-46-159.hsd1.ca.comcast.net / 98.248.46.159
NAT detection (?): NAT Detected
Your global IP address is 98.248.46.159 while your local one is 192.168.1.50. You are behind a NAT. Your local address is in unroutable address space.
Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.
Local Network Interfaces (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
DNS-based host information (?): OK
You are not a Tor exit node for HTTP traffic.
You are listed on the
Spamhaus
Policy Based Blacklist,
meaning that your provider has designated your address block as
one that should only be sending authenticated email, email through the ISP's
mail server, or using webmail.
The
SORBS DUHL
believes you are using a statically assigned IP address.
TCP connectivity (?): Not executed
Direct TCP access to remote FTP servers (port 21)
is allowed.
Direct TCP access to remote SSH servers (port 22)
is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80)
is allowed.
Direct TCP access to remote POP3 servers (port 110)
is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143)
is allowed.
Direct TCP access to remote SNMP servers (port 161)
is allowed.
Direct TCP access to remote HTTPS servers (port 443)
is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465)
is allowed.
Direct TCP access to remote secure IMAP servers (port 585)
is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587)
is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993)
is allowed.
Direct TCP access to remote POP/SSL servers (port 995)
is allowed.
Direct TCP access to remote SIP servers (port 5060)
is allowed.
Direct TCP access to remote BitTorrent servers (port 6881)
is allowed.
UDP connectivity (?): OK
Basic UDP access is available.
Direct UDP access to remote DNS servers (port 53) is allowed.
Traceroute (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
Path MTU (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
Network latency measurements (?): Latency: 81ms Loss: 0.0%
The round-trip time (RTT) between your computer and
our server is 81 msec, which is good.
We recorded no packet loss between your system and our server.
TCP connection setup latency (?): 91ms
The time it takes your computer to set up a TCP
connection with our server is 91 msec, which is good.
Network background health measurement (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
Network bandwidth measurements (?): Upload 11 Mbit/sec, Download >20 Mbit/sec
Your Uplink: We measured your uplink's
sending bandwidth at 11 Mbit/sec. This level of bandwidth works well
for many users.
Your Downlink: We measured your downlink's
receiving bandwidth at >20 Mbit/sec. This level of bandwidth works well
for many users.
During this test, the applet observed 3 reordered packets.
During this test, the applet observed 3 reordered packets.
Network buffer measurements (?): Uplink 180 ms, Downlink is good
We estimate your uplink as having 180 msec of buffering.
This level may serve well for maximizing speed while minimizing the
impact of large transfers on other traffic.
We were not able to produce enough traffic
to load the downlink buffer, or the downlink buffer is particularly
small. You probably have excellent behavior when downloading files and
attempting to do other tasks.
Address-based HTTP proxy detection (?): OK
We detected no explicit sign of HTTP proxy via IP address changes.
Content-based HTTP proxy detection (?): OK
No HTTP header or content changes hint at the presence of a proxy.
HTTP proxy detection via malformed requests (?): OK
Deliberately malformed HTTP requests arrive at our server
unchanged. We are not able to detect a proxy along the path to our
server using this method.
Filetype-based filtering (?): OK
We did not detect file-content filtering.
HTTP caching behavior (?): OK
We detected no signs of a transparent HTTP cache in your network path.
JavaScript-based tests (?): OK
The applet did not execute within a frame.
Your web browser reports the following cookies for our web page:
- netAlizEd (set by our server)
Your web browser was unable to fetch an image using IPv6.
Restricted domain DNS lookup (?): Failed
Restricted DNS lookup test failed to complete.
Unrestricted domain DNS lookup (?): Failed
Unable to lookup a name not associated with our server.
Direct DNS support (?): OK
All tested DNS types were received OK.
Direct EDNS support (?): Note
EDNS-enabled requests for small responses remain unanswered. This
suggests that a proxy or firewall is unable to handle extended DNS
requests.
EDNS-enabled requests for medium-sized responses remain unanswered.
This suggests that a proxy or firewall is unable to handle extended
DNS requests or DNS requests larger than 512 bytes.
EDNS-enabled requests for large responses are answered
successfully.
DNS resolver address (?): OK
The IP address of your ISP's DNS Resolver is 98.248.46.159, which resolves to c-98-248-46-159.hsd1.ca.comcast.net.
DNS resolver properties (?): Lookup latency 15ms
Your ISP's DNS resolver requires 15 msec to conduct
an external lookup, and 1 msec to lookup an item in the cache.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver requests DNSSEC records.
Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes.
Your DNS resolver can successfully receive a
large (>1500 byte) DNS response.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS resolver respects a TTL of 0 seconds.
Your ISP's DNS resolver respects a TTL of 1 seconds.
No transport problems were discovered which could affect
the deployment of DNSSEC.
DNS glue policy (?): Failed
Your ISP's DNS resolver does not accept generic additional (glue) records — good.
Your ISP's DNS resolver accepts additional (glue) records for
nameservers located in subdomains of the queried domain.
DNS resolver port randomization (?): OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.
DNS lookups of popular domains (?): OK
74 of 74 popular names were resolved successfully.
In the following table reverse lookups that failed but for which a
Start Of Authority (SOA) entry indicated correct name associations are
shown using an "X", followed by the SOA entry. Absence of both IP
address and reverse name indicates failed forward lookups.
4 popular names have a mild anomaly. The ownership suggested by the
reverse name lookup does not match our understanding of the original
name. The most likely cause is the site's use of a Content Delivery
Network.
| Name | IP Address | Reverse Name/SOA |
|---|---|---|
| www.f-secure.com | 77.67.91.98 | X (ns-pri.ripe.net) |
| www.irs.gov | 77.67.91.122 | X (ns-pri.ripe.net) |
| www.postbank.de | 195.50.155.73 | X (ns1.arcor-ip.de) |
| www.visa.com | 77.67.91.112 | X (ns-pri.ripe.net) |
DNS external proxy (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
DNS results wildcarding (?): OK
Your ISP correctly leaves non-resolving names untouched.
DNS-level redirection of specific sites (?): OK
Your ISP does not appear to be using DNS to redirect
traffic for specific websites.
DNS support for IPv6 (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
IPv4, IPv6, and your web browser (?): Not executed
JavaScript is not enabled for the Netalyzr site.
IPv6 connectivity (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
System clock accuracy (?): Not executed
The test was not executed. Required functionality was unavailable
or not permitted, or this session dates from a time before Netalyzr
supported this test.
Browser properties (?): OK
Your web browser sends the following parameters to all web sites
you visit:
- User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 GTB5 (.NET CLR 3.5.30729)
- Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8
- Accept Language: en-us,en;q=0.5
- Accept Encoding: gzip,deflate
- Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Uploaded data (?): OK
The applet uploaded no additional data.