Hostname
sljaka.com
Last fetched
sljaka.com resolves to 104.21.74.65, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. sljaka.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.74.65
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.199.237
172.67.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 195.201.197.85
195.201.0.0/16 · HETZNER-AS - Hetzner Online GmbH · Falkenstein, DE
IPv6 resolution
Attribution
Cloudflare
cdn · MAIL_RECEIVER, ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:440
- Registrant organisation
- int. websites. pk
- Contact emails
- sljaka.com@domainsbyproxy.com, contact@sljaka.com, darkokerekes@yahoo.co.uk
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- carrera.ns.cloudflare.com
- ricardo.ns.cloudflare.com
- dns1.dwhost.net
- dns2.dwhost.net
- dns3.dwhost.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- sljaka.com
- _dc-mx.05aa1de8554d.sljaka.com
SPF policy
- a: sljaka.com
- mx: sljaka.com
- ip: 136.243.82.147
- ip: 195.201.175.101
- ip: 195.201.197.85
Threat-feed evidence
History
Related pages
Pivot from sljaka.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "sljaka.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.