Hostname
propersky.com
Last fetched
propersky.com resolves to 2 IPv4 addresses operated by AS209242 in US. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
propersky.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 199.60.103.179 | 199.60.151.0/24 | AS209242 | — | US |
| 199.60.103.79 | 199.60.151.0/24 | AS209242 | — | US |
WHOIS identity
- Registrar
- iana:1068
- Organization
- jim smith
- Contact emails
Subdomains
20 observed subdomains of propersky.com.
Showing 19 of 20. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from propersky.com in the public web crawl.
25 sites link to this hostname.
206 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
20 SPF mechanisms authorising senders for propersky.com.
| Mechanism | Target |
|---|---|
| SPF_A | propersky.com |
| SPF_INCLUDE | 24067378.spf03.hubspotemail.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.us.exclaimer.net |
| SPF_INCLUDE | transmail.net |
| SPF_INCLUDE | u3348989.wl240.sendgrid.net |
| SPF_INCLUDE | zcsend.net |
| SPF_IP | 108.52.203.242 |
| SPF_IP | 13.82.228.43 |
| SPF_IP | 167.89.70.61/32 |
| SPF_IP | 208.94.147.128/32 |
| SPF_IP | 34.192.37.131 |
| SPF_IP | 40.117.44.182 |
| SPF_IP | 40.121.154.115 |
| SPF_IP | 40.121.158.167 |
| SPF_IP | 40.71.11.140 |
| SPF_IP | 50.31.33.121/32 |
| SPF_IP | 52.3.110.62 |
| SPF_IP | 52.44.160.38 |
| SPF_IP | 64.94.35.32/32 |
Related pages
Pivot deeper into the graph from propersky.com.
- IP · 199.60.103.179
- ASN · AS209242
- Registrar · iana:1068
- Country · US
- Email · 5a9e1f1dc8e847478e35353bd961ff19.protect@whoisguard.com
- TLD · .com
- Browse hostnames · pr…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "propersky.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.