159.49.240.6 - IP in United States, - Comments and Complaints

IP: 159.49.240.6

Location: United States

IP:

159.49.240.6 note

note

Country:

United States

B Class:

159.49.0.0 - 159.49.255.255

Latitude:

37.751

Longitude:

-97.822

Whois** information (click to hide)

NetRange: 159.49.0.0 - 159.49.255.255
CIDR: 159.49.0.0/16
NetName: ALASKA-AIRGROUP-159-49
NetHandle: NET-159-49-0-0-1
Parent: NET159 (NET-159-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Alaska Airlines, Inc. (ALASKA)
RegDate: 1992-03-06
Updated: 2024-09-03
Ref: https://rdap.arin.net/registry/ip/159.49.0.0

OrgName: Alaska Airlines, Inc.
OrgId: ALASKA
Address: 20313 28th Ave S
City: Seatac
StateProv: WA
PostalCode: 98198
Country: US
RegDate: 1992-03-06
Updated: 2024-09-03
Ref: https://rdap.arin.net/registry/entity/ALASKA

OrgTechHandle: JS19-ARIN
OrgTechName: Spence, John
OrgTechPhone: +1-206-574-4860
OrgTechEmail: john.spence@alaskaair.com
OrgTechRef: https://rdap.arin.net/registry/entity/JS19-ARIN

OrgNOCHandle: NOC32507-ARIN
OrgNOCName: NOC
OrgNOCPhone: +1-206-433-3200
OrgNOCEmail: noc@alaskaair.com
OrgNOCRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

OrgTechHandle: VILLA710-ARIN
OrgTechName: Villar, Jennifer
OrgTechPhone: +1-206-392-8747
OrgTechEmail: jennifer.villar@alaskaair.com
OrgTechRef: https://rdap.arin.net/registry/entity/VILLA710-ARIN

OrgTechHandle: NOC32507-ARIN
OrgTechName: NOC
OrgTechPhone: +1-206-433-3200
OrgTechEmail: noc@alaskaair.com
OrgTechRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

OrgAbuseHandle: NOC32507-ARIN
OrgAbuseName: NOC
OrgAbusePhone: +1-206-433-3200
OrgAbuseEmail: noc@alaskaair.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

OrgTechHandle: TVK-ARIN
OrgTechName: Thadi, Vipin Krishna
OrgTechPhone: +1-206-433-3200
OrgTechEmail: vipin.thadi@alaskaair.com
OrgTechRef: https://rdap.arin.net/registry/entity/TVK-ARIN

OrgTechHandle: FENDE9-ARIN
OrgTechName: Fender, Jeremy
OrgTechPhone: +1-252-764-1871
OrgTechEmail: jeremy.fender@alaskaair.com
OrgTechRef: https://rdap.arin.net/registry/entity/FENDE9-ARIN

RTechHandle: FENDE9-ARIN
RTechName: Fender, Jeremy
RTechPhone: +1-252-764-1871
RTechEmail: jeremy.fender@alaskaair.com
RTechRef: https://rdap.arin.net/registry/entity/FENDE9-ARIN

RAbuseHandle: NOC32507-ARIN
RAbuseName: NOC
RAbusePhone: +1-206-433-3200
RAbuseEmail: noc@alaskaair.com
RAbuseRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

RTechHandle: TVK-ARIN
RTechName: Thadi, Vipin Krishna
RTechPhone: +1-206-433-3200
RTechEmail: vipin.thadi@alaskaair.com
RTechRef: https://rdap.arin.net/registry/entity/TVK-ARIN

RTechHandle: JS19-ARIN
RTechName: Spence, John
RTechPhone: +1-206-574-4860
RTechEmail: john.spence@alaskaair.com
RTechRef: https://rdap.arin.net/registry/entity/JS19-ARIN

RNOCHandle: NOC32507-ARIN
RNOCName: NOC
RNOCPhone: +1-206-433-3200
RNOCEmail: noc@alaskaair.com
RNOCRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

RTechHandle: NOC32507-ARIN
RTechName: NOC
RTechPhone: +1-206-433-3200
RTechEmail: noc@alaskaair.com
RTechRef: https://rdap.arin.net/registry/entity/NOC32507-ARIN

DNS BlackList result:

Most recent complaints on 159.49.240.6

No comments submitted yet.

Complaints

Please help us keep Internet safer and cleaner by leaving a descriptive comment about 159.49.240.6 IP address

Frequently Asked Questions:

- Report emails (spam/fraud/threats)
- Hacked Gmail accounts
- WordPress Hacking Attempts
- SSH Hacking Attempts
- Why Can't I See The Exact Address?

IP addresses with same latency:

United States

Russia

United States

Singapore

DNSBL* - is a list of IP addresses published through the Internet Domain Name Service (DNS) either as a zone file that can be used by DNS server software, or as a live DNS zone that can be queried in real-time. DNSBLs are most often used to publish the addresses of computers or networks linked to spamming; most mail server software can be configured to reject or flag messages which have been sent from a site listed on one or more such lists.

WHOIS** - is a query/response protocol that is widely used for querying databases in order to determine the registrant or assignee of Internet resources, such as a domain name, an IP address block, or an autonomous system number. WHOIS lookups were traditionally performed with a command line interface application, and network administrators predominantly still use this method, but many simplified web-based tools exist. WHOIS services are typically communicated using the Transmission Control Protocol (TCP). Servers listen to requests on the well-known port number 43.

** Approximate Geographic Location - This is NOT the exact geographical location of the person/organization with the given IP address. However, this should still give you a good idea about the area/region where this person/orgranization is located.