Hostname
cruisebase.com
Last fetched
cruisebase.com resolves to 2 IPv4 addresses operated by INCAPSULA - Incapsula Inc in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
cruisebase.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 |
|---|---|---|---|---|
| 45.60.63.164 | 45.60.63.0/24 | AS19551 | INCAPSULA - Incapsula Inc | US |
| 45.60.65.164 | 45.60.65.0/24 | AS19551 | INCAPSULA - Incapsula Inc | GB |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of cruisebase.com owner
- Contact emails
- operations@travtech.com
- jlawless@owt.net
- 79ffd5d9-59fe-4d8e-b66f-cc4d4dfce79f@identity-protect.org
- 930cbd24-42bf-40e0-8d5e-3450dbb6ce91@identity-protect.org
- 9371f253-d797-4112-bbdc-466fd0f93935@identity-protect.org
- 9b868c13-1941-4234-986b-e7d29922c2ab@identity-protect.org
- b090a323-51a5-42ec-b86e-066c7b5e3df6@identity-protect.org
- bc97f628-6047-4e37-b3f5-b3aeffa8ea5a@identity-protect.org
- f85e78e9-5eef-4cb8-bd7d-cd28e75fb6d8@identity-protect.org
- owner-3757508@cruisebase.com.whoisprivacyservice.org
Subdomains
9 observed subdomains of cruisebase.com.
Web-graph footprint
Distinct hostnames that link to or from cruisebase.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
4 SPF mechanisms authorising senders for cruisebase.com.
| Mechanism | Target |
|---|---|
| SPF_IP | 184.72.100.159 |
| SPF_IP | 184.72.111.86 |
| SPF_IP | 54.208.242.158 |
| SPF_MX | cruisebase.com |
Related pages
Pivot deeper into the graph from cruisebase.com.
- IP · 45.60.63.164
- ASN · AS19551INCAPSULA - Incapsula Inc
- Registrar · iana:468
- Country · US
- Email · operations@travtech.com
- TLD · .com
- Browse hostnames · cr…
- 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: "cruisebase.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.