Hostname
xcimaoceans.com
Last fetched
xcimaoceans.com resolves to 1 IPv4 address operated by GOOGLE-2 - Google LLC in NL. WHOIS lists iana:1001 as the registrar.
Nutrition Label
Resolution chain
xcimaoceans.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 35.214.236.26 | 35.214.128.0/17 | AS19527 | GOOGLE-2 - Google LLC | NL |
WHOIS identity
- Registrar
- iana:1001
- Organization
- mediehuset bergen as
- Contact emails
- 4c8u9qgzfxi3@privacy-protection.email
- agtftbatxak6@privacy-protection.email
- d3yhjm6bdyqk@privacy-protection.email
- ebnwawnvunu5@privacy-protection.email
- fd9dxzux94ht@privacy-protection.email
- mud7v5sgzkbv@privacy-protection.email
- p3t8gbdi4uvs@privacy-protection.email
- tk7tpfvkzva3@privacy-protection.email
- tsw7xz7pdbsf@privacy-protection.email
- txozk6abra58@privacy-protection.email
- udjdsbzdh3bt@privacy-protection.email
- uwyjjs7fjdf2@privacy-protection.email
- v484zmmgpvfv@privacy-protection.email
- x7ho6fzesppp@privacy-protection.email
- xr36cvbey9tg@privacy-protection.email
- y3ihfeqdmfgn@privacy-protection.email
Subdomains
1 observed subdomain of xcimaoceans.com.
| Subdomain |
|---|
| www.xcimaoceans.com |
Web-graph footprint
Distinct hostnames that link to or from xcimaoceans.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for xcimaoceans.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.domeneshop.no |
Related pages
Pivot deeper into the graph from xcimaoceans.com.
- IP · 35.214.236.26
- ASN · AS19527GOOGLE-2 - Google LLC
- Registrar · iana:1001
- Country · NL
- Email · 4c8u9qgzfxi3@privacy-protection.email
- TLD · .com
- Browse hostnames · xc…
- 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: "xcimaoceans.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.